modscode JA

modscode / Gallery / spec-flow

spec-flow

[mod] [skills] Turns a feature request into a spec, one approved step at a time: clarify the request (asking you what is unclear), survey every affected screen and feature with subagents, write the requirements, then propose several featur…

Code you can checkTerminal + desktopPaneBandToastBoxButtonText

What it does

  • Draws a band above the prompt, a pane, toasts
  • Adds /specs
  • Watches tool calls
  • Hooks session.start, turn.complete

Good points

  • No network calls
  • Starts no processes
  • Small: 251 lines
  • Handles errors

Code to start from

Two kinds: a starter modscode writes from the design above, and the lines of the mod's own code that draw it.

Starter (register.tsx)

register.tsx
import type { Register } from 'claude-code'

// Drawn like spec-flow by japan-da-man (pane, band, toast), as modscode read it from the mod's code:
// https://modscode.com/gallery/japan-da-man-spec-flow/
// Written by modscode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
  // the band above the prompt; what else goes there is drawn under it
  on('ui.render', { component: 'AbovePrompt' }, async ($, e, next) => {
    const { Box, Text, Button } = $.ui.resolve(e)
    const title = '…'
    const MARKS = '…'
    const label = '…'
    return (
      <Box flexDirection="column">
        <Box flexDirection="row" gap={2} paddingX={1}>
          <Text color="cyan" bold wrap="truncate-end">
            {`◆ ${title}`}
          </Text>
          <Text color="green">
            {`${MARKS} ${label}`}
          </Text>
          <Text color="green">
            {`${MARKS} ${label}`}
          </Text>
          <Text color="green">
            {`${MARKS} ${label}`}
          </Text>
          <Button label="Specs" hotkey="s" />
        </Box>
        {await next(e)}
      </Box>
    )
  })

  // the pane: open it with $.ui.open({ id: 'my-pane', title: "spec-flow" })
  on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
    const { Box, Text, Button } = $.ui.resolve(e)
    const title = '…'
    const id = '…'
    const label = '…'
    const file = '…'
    const file2 = '…'
    const file3 = '…'
    const file4 = '…'
    const file5 = '…'
    const file6 = '…'
    const file7 = '…'
    const file8 = '…'
    const file9 = '…'
    return (
      <Box flexDirection="column">
        <Box flexDirection="column" marginBottom={1}>
          <Text bold color="green">
            {`✔ ${title}`}
          </Text>
          <Text dimColor>
            {`docs/specs/${id}`}
          </Text>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file2}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file3}
            </Text>
          </Box>
        </Box>
        <Box flexDirection="column" marginBottom={1}>
          <Text bold color="green">
            {`✔ ${title}`}
          </Text>
          <Text dimColor>
            {`docs/specs/${id}`}
          </Text>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file4}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file5}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file6}
            </Text>
          </Box>
        </Box>
        <Box flexDirection="column" marginBottom={1}>
          <Text bold color="green">
            {`✔ ${title}`}
          </Text>
          <Text dimColor>
            {`docs/specs/${id}`}
          </Text>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file7}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file8}
            </Text>
          </Box>
          <Box flexDirection="row" gap={1}>
            <Button label="[ ]" plain />
            <Text color="yellow">
              {`${label}  確認待ち(チェックで承認して次へ)`}
            </Text>
            <Text dimColor wrap="truncate-start">
              {file9}
            </Text>
          </Box>
        </Box>
        <Text dimColor>
          [x] 承認済み · [?] 確認待ち · [~] 作業中 · Tab で移動 · Esc で閉じる
        </Text>
      </Box>
    )
  })

  on('session.start', async ($, e, next) => {
    const path = '…'
    await $.ui.toast(`spec-flow: Claude に送れませんでした`)
    await $.ui.toast(`spec-flow: ${path} を書き換えられませんでした`)
    return next(e)
  })
}

The mod's own code

Its licence text was not found at the commit read, so only the places in the source are linked.

What its code calls

writes filesdrives Claudetool calls

The design, read from code

Drawn from the mod's source at the commit read, not from a run: a list is drawn three times, a condition takes its first branch that draws in the desktop app, and a value only the run time knows is shown as a made-up sample (dotted underline) or left out. Colours and type are this site's.

What its code shows

Read from the source at commit b6e772f04233 on 2026-10-06. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.

Decides the listing: code you can check
Entry readEvery module hooks/hooks.json names was read.plugins/spec-flow/hooks/register.js
ParsesEvery file parses as TypeScript or JavaScript.1 files parsed
All its code is in the modEvery import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod
ReadableNo minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs
Calls in the openNetwork and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open
For you to weigh before installing
Where it drawsThe terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both
Install lineWhether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there
Programs on WindowsWhether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks
NetworkWhether every fetch names its https host in the code.no network
ProgramsWhether every program it starts is named in the code and is not a shell, an interpreter or a network tool.starts no programs
Reads and sendsWhether it both reads files or environment variables and reaches the network.reaches no network
Keys in the sourceWhether the source holds what looks like an API key or a private key.no keys in the source
LicenceAn open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets modscode show its code; otherwise the code is linked.no licence

This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen

Install it

Check it yourself before you install it. Mods run unsandboxed, with your permissions, and modscode does not vouch for what this code does. Read the code below (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.

Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:

/plugin marketplace add japan-da-man/claude-code
/plugin install spec-flow@japan-da-man

This installs the marketplace's latest commit, which may not be the one read here (b6e772f04233). Compare them before you install.

Ask Claude about it

With the modscode connector added, Claude can read this design, what its code reaches and its code, and build on them. Ask it like this:

Read the modscode design "japan-da-man-spec-flow" with its code and make me a pane like it

Search them from Claude: the MCP connector

Similar designs