Loading...
Loading...
Found 9 Skills
Stage 2 code quality review. Triggers: 'quality review', 'check code quality', or /review stage 2. Requires spec-review to have passed first. Checks SOLID, DRY, security, and test quality. Do NOT use for spec compliance — use spec-review instead.
High-velocity solo development workflow. Idea to production same-day. 9 commands: plan, spike, ship, review, spec-review, focus, done, drop, workflow. Auto-activates on: "plan", "spec", "ship", "spike", "spec-review", "review spec", "analyze spec", "challenge spec", "focus", "what should i do", "prioritize", "overwhelmed", "what should i work on", "done", "finish", "complete", "drop", "abandon", "workflow", "what's next", "whats next", "next step", "what now".
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
Validate a plan or spec before implementation using multi-model council. Answer: Is this good enough to implement? Triggers: "pre-mortem", "validate plan", "validate spec", "is this ready".
A professional tool for generating customized checklists for current features based on user requirements. Specifically designed for requirement quality validation, it creates "English-style unit tests" to verify the completeness, clarity, and consistency of requirements. Trigger words: speckit-checklist, checklist, requirements validation, quality check, quality review, spec review
Use when a Spec Kit feature has `spec.md` and you need a requirements-quality checklist (clarity, completeness, consistency, measurability, coverage), not implementation/runtime test cases.
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.
Analyze two functional specs from a ***plain spec file to determine if they conflict. Use when the user wants to check whether two specific functional requirements are compatible, or when debugging a suspected conflict between two specs.
Review a spec or concrete code changes and report evidence-backed bugs, regressions, and risks.