Loading...
Loading...
Found 30 Skills
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 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 or update `{FEATURE_DIR}/verification/usecase.md` (test cases) during the verification phase of the Spec Pack, and require AC traceability and a structure that supports automated script generation.
Used to confirm that development is completed and ensure all tests/checks have passed
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.
Use this when you need to execute R2 in the sdlc-dev product requirement Spec process, transcribe requirements/solution.md into a deliverable, acceptable, and testable requirements/prd.md, while avoiding guessing file paths, continuing generation when solution.md is missing, or using "Pending Questions/Open Questions" to replace the verification checklist.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth (SSOT) for execution checklist and status), and provide an unambiguous task list for subsequent I2 execution.
Use when working on the spec branch of sdlc-dev, when requirements are ambiguous, scope is unstable, constraints are unclear, and issues such as context drift, unfounded assumptions, multiple questions asked at once, or requests to skip the FEATURE_DIR/raw gate occur.
Use when you need to produce a D2 decision document (RFC/Decision Doc) for a Spec Pack, and need to independently decide whether to execute D0 (bypass design via diversion) and D1 (optional research) even under pressure, avoiding guessing FEATURE_DIR, making up input details, writing design as implementation specifics, or leaving behind TODO/To-Confirm lists.
Use when you need to perform D1 research during the Spec-level design phase (output `{FEATURE_DIR}/design/research.md`), or when you face critical uncertainties/high-risk points that require verification first instead of directly proceeding to D2; common symptoms include lack of evidence to support trade-offs, unknown items written as TODOs/to-be-confirmed issues, attempting to guess the FEATURE_DIR under pressure, or writing research as implementation details.
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.