| name | speckit.analyze |
| description | 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. |
Speckit Analyze Command Executor
This skill executes the official GitHub Speckit /speckit.analyze command.
Execution Protocol
When this skill is invoked, you MUST:
1. Load the Original Command File
Read and parse .opencode/commands/speckit.analyze.md from the current project directory.
2. Process OpenCode Command Syntax
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 |
3. Execute the Processed Instructions
After syntax processing, follow all instructions in the command file exactly as written, including:
- Running
.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
- Loading spec.md, plan.md, tasks.md, and constitution.md
- Performing detection passes (duplication, ambiguity, coverage gaps, etc.)
- Producing analysis report with severity assignments
- STRICTLY READ-ONLY: Do not modify any files
4. Maintain Speckit Workflow Integrity
- Honor constitution as non-negotiable authority
- Suggest remediation but do NOT auto-apply
- Recommend
/speckit.implement if no CRITICAL issues
User Input
$ARGUMENTS
Fallback
If .opencode/commands/speckit.analyze.md does not exist, check for:
.opencode/command/speckit.analyze.md (legacy path)
If no command file is found, report an error and suggest running specify init first.
