メニュー
Writes or updates the capability spec for the current feature branch from a prose description or context file passed via $ARGUMENTS.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | spec |
| description | Writes or updates the capability spec for the current feature branch from a prose description or context file passed via $ARGUMENTS. |
| model | opus |
| disable-model-invocation | true |
Translates a feature description into a living capability specification. The spec is the single source of truth for what the feature must do — no test stubs, no implementation.
$ARGUMENTS — required. The feature description as text. Use @path syntax to inline
a context file (e.g. /spec @.claude/tmp/MXB-7.md), or pass prose directly.
If empty, ask the user to describe the feature.
Use $ARGUMENTS as the feature description.
Scan src/features/ for existing feature folders:
ls src/features/ 2>/dev/null || echo "(none)"
Map the description to an existing feature if it clearly enhances one. Otherwise
derive a short, lowercase, hyphenated name from the domain (e.g. todo-list,
auth, user-profile).
If specs/<feature>/spec.md already exists, read it first, then update it to reflect
the new requirements — preserving existing scenarios that remain valid.
If it does not exist, create it:
# <Feature> Specification
## Purpose
<What this capability does and why it exists. 2-4 sentences.>
## Requirements
### <Requirement Name>
The system SHALL <requirement statement>.
#### Scenario: <scenario name>
- GIVEN <precondition>
- WHEN <action>
- THEN <expected outcome>
Write one Requirement block per distinct behaviour. Scenarios must be concrete and testable.
git add specs/
git commit -m "docs: spec <feature>"
Print:
specs/<feature>/spec.md)specs/ are permanent — never delete themImplements the feature changes introduced by spec changes on the current branch. Writes tests, runs quality checks, and commits.
Reads the capability specs changed on this branch and writes a technical plan. Optional — skip for straightforward changes and go straight to /code.
End-to-end delivery skill — takes a Linear issue ID or a description, runs the appropriate pipeline (spec → plan → code → review), and handles all git and Linear orchestration.
PR review skill — fetches active GitHub Copilot review comments on a PR, critically evaluates each suggestion, implements those that improve code posture, and dismisses those that don't add value.