Loading...
Loading...
Found 53 Skills
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use this when you are about to start Discover for an existing project, but you don't know "which portals can be used as evidence (run/test/ci/contract/ops)" and "which modules should be prioritized (P0/P1/P2)", and you are worried that out-of-control scope will lead to unmaintainable results.
Use when you need to generate/update test plans, test cases, test suites or test reports during the verification phase of Spec Pack, and require strict access control, traceable artifact storage, and no unauthorized routing.
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.
Use when you already have a components map and multiple module pages, and now need to converge business modules (products <= 6), fix the entry points for operation, troubleshooting and rollback (ops), and implement DoD access control and incremental Discover (Delta Discover, stale expiration detection) to ensure the knowledge base is usable and maintainable.
Use when you need to create defect reports that can be directly pasted into external defect systems (without saving bug files in the Spec Pack) during the verification phase of the Spec Pack, and write the defect references back to `{FEATURE_DIR}/verification/report-*.md`.
Start Task
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Bug-to-test pipeline: reproduce the bug as a failing test first, then fix. The regression test lives forever.
Make all tech decisions, write CLAUDE.md, scaffold the project, and get a smoke test passing. Run after /wireframe.
Generate clickable HTML wireframes for every screen in the PRD. No design tool needed — open in browser.
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.