メニュー
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. Use after /speckit.specify to resolve ambiguities before research and evaluation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | speckit.clarify |
| description | Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. Use after /speckit.specify to resolve ambiguities before research and evaluation. |
This skill executes the official GitHub Speckit /speckit.clarify command.
When this skill is invoked, you MUST:
Read and parse .opencode/commands/speckit.clarify.md from the current project directory.
The command file uses special syntax that MUST be processed before execution:
| Syntax | Action |
|---|---|
$ARGUMENTS | Replace with user-provided arguments |
$1, $2, etc. | Replace with positional arguments |
@filepath | Read the file at filepath and insert its full contents |
!command`` | Execute the shell command and insert its stdout |
After syntax processing, follow all instructions in the command file exactly as written, including:
.specify/scripts/powershell/check-prerequisites.ps1 -Json -PathsOnlyhandoffs defined in the command's YAML frontmatter/speckit.research (NOT /speckit.plan directly)After clarify is complete:
clarified/speckit.research$ARGUMENTS
If .opencode/commands/speckit.clarify.md does not exist, check for:
.opencode/command/speckit.clarify.md (legacy path)If no command file is found, report an error and suggest running specify init first.
Phase 11 Multi-Persona Product Review. Evaluates final product from 10 different professional perspectives to ensure real-world readiness. Triggered after Phase 10 Quality Score passes (>= 80).
MANDATORY workflow for GitHub Speckit projects. Enforces Spec-First → Clarify → Research → Evaluate → Design → Plan → TDD → Review, with optional Constitution and quality checks. Activates when working in projects with .github/speckit/ directory.
Spawn parallel worker terminals to execute multi-domain tasks concurrently. Use when 3+ independent tasks span 2+ domains (frontend, backend, testing, security, etc.)
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. Use to identify inconsistencies before implementation.
Generate a custom checklist for the current feature based on user requirements. Checklists are "unit tests for requirements" - they validate quality, clarity, and completeness of requirements in a given domain.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync. Use when starting a new Speckit project or updating project principles.