Requirements Spec Kit

Overview

Decision Flow: Create New or Append to Existing

• Decide immediately based on user input: Append if there is a SPEC-ID, spec.md path, or "append/existing" instruction.
• If unsure, search for existing SPECs: Confirm matches using

  rg -n "# 機能仕様:" specs/SPEC-*/spec.md

  and main keywords.
• If there is exactly one match, append to it. If there are multiple matches, present the candidates (SPEC-ID and title) and ask for selection.
• If no matches are found, create a new one.
• When appending, work in the worktree/feature branch of the target SPEC (

  .specify/scripts/bash/check-prerequisites.sh

  is used to select the latest SPEC).

Workflow (specify → clarify → plan → tasks)

1) specify

• Read

  .specify/templates/commands/specify.md

  and execute the script described once.
• Use

  .specify/templates/spec-template.md

  to fill in spec.md in Japanese.
• When creating a new SPEC, move to the

  WORKTREE_PATH

  output by the script before proceeding with subsequent work.
• When appending to an existing SPEC, only update the relevant sections and maintain sequential numbers such as heading order and FR numbers.
• If TDD/test requirements are specified, clearly state that "automated testing is required" in the requirements or success criteria.
• Update

  specs/specs.md

  , and be sure to include priority and status (the same applies when using

  update-spec-index.sh

  ).

2) clarify

• Follow

  .specify/templates/commands/clarify.md

  .
• Limit questions to a maximum of 5 and present recommended answers.
• Immediately reflect the answers in the corresponding sections of spec.md.

3) plan

• Follow

  .specify/templates/commands/plan.md

  .
• Refer to

  .specify/memory/constitution.md

  to meet the gate evaluation requirements.
• Generate outputs (plan.md / research.md / data-model.md / quickstart.md / contracts/).

4) tasks

• Follow

  .specify/templates/commands/tasks.md

  .
• If TDD/test requirements are specified, be sure to include test tasks.
• Strictly adhere to the checklist format (ID/Story/File Path) of tasks.md.

Output Reporting

• Report the paths of the generated/updated spec.md, plan.md, and tasks.md.
• If there are unresolved clarifications, obtain user answers before proceeding.