Turn a Rough Request into a Tech Spec

Use this when

You have a vague idea or stakeholder request and need to turn it into a concrete, implementable technical specification.

Skill	Role
`/req-analyze`	Decompose requirements, stakeholder scan, structuring
`/feasibility-study`	Evaluate solution approaches with quantitative comparison
`/tech-spec`	Generate the technical specification document
`/review-spec`	Review spec for completeness and feasibility
`/codex-brainstorm`	Adversarial debate for design decisions

/req-analyze — decompose the request into structured requirements (produces 1-requirements.md)
/feasibility-study — evaluate 2-3 solution approaches with trade-off analysis
/codex-brainstorm — adversarial debate on key design decisions (Nash equilibrium)
/tech-spec — generate the full technical spec (produces 2-tech-spec.md)
/review-spec — review for completeness, feasibility, and risk coverage
/create-request — create a trackable request doc with acceptance criteria

Situation	Choice
Request is well-defined already?	Skip `/req-analyze`, go straight to `/feasibility-study`
Only one viable approach?	Skip `/feasibility-study`, go to `/tech-spec`
Key design decision is controversial?	`/codex-brainstorm` for adversarial validation
Need architecture diagram?	Add `/architecture` after `/tech-spec`
Want PM/CTO summary?	`/project-brief` to convert spec into executive summary

Gate	Enforced by	Sentinel
Spec review	Behavior (not hook-enforced)	`✅ Approved` / `⚠️ Needs revision` / `❌ Needs redesign`

This is a planning workflow — no hook enforcement. Quality is validated by /review-spec.