jnuyens/bm:spec-phase
dist/bm/skills/spec-phase/SKILL.md
Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.
$ install --global
skillsauthnpx skillsauth add jnuyens/gsd-plugin bm:spec-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 14, 2026, 2:28 AM145.7s1 file scanned
SKILL.md
- name:
- bm:spec-phase
- description:
- Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.
- argument-hint:
- <phase> [--auto] [--text]
<objective>
Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.
Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify
How it works:
- Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
- Scout the codebase — understand current state before asking questions
- Run Socratic interview loop (up to 6 rounds, rotating perspectives)
- Score ambiguity across 4 weighted dimensions after each round
- Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
- Commit SPEC.md — discuss-phase picks it up automatically on next run
Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"
</objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/spec-phase.md @${CLAUDE_PLUGIN_ROOT}/templates/spec.md </execution_context>
<context> Phase number: $ARGUMENTS (required)Flags:
--auto— Skip interactive questions; Claude selects recommended defaults and writes SPEC.md--text— Use plain-text numbered lists instead of TUI menus (required for/rcremote sessions)
Context files are resolved in-workflow using init phase-op.
</context>
MANDATORY: Read the workflow file BEFORE taking any action. Do not improvise from the objective summary above. </process>
<success_criteria>
- Codebase scouted for current state before questioning begins
- All 4 ambiguity dimensions scored after each interview round
- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
- SPEC.md committed atomically
- User knows they can now run /bm:discuss-phase which will load SPEC.md automatically </success_criteria>
Related Skills
jnuyens/bm:workstreams
tools
VerifiedTrustedCommunity
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
73SKILL.mdUpdated Jul 14, 2026
jnuyens/bm:version
tools
VerifiedTrustedCommunity
Print the installed GSD plugin version and check online for updates
73SKILL.mdUpdated Jul 14, 2026
jnuyens/bm:verify-work
testing
VerifiedTrustedCommunity
Validate built features through conversational UAT
73SKILL.mdUpdated Jul 14, 2026
jnuyens/bm:validate-phase
testing
VerifiedTrustedCommunity
Retroactively audit and fill Nyquist validation gaps for a completed phase
73SKILL.mdUpdated Jul 14, 2026