Loading...
Loading...
Found 3 Skills
Use this when you need to execute R4 (generate an interactive Demo project based on requirements/prototype.md) in the sdlc-dev product requirement Spec process, and need to avoid skipping spec-context, proceeding when prototype.md is missing or the runnable Demo project root directory is missing, or creating custom pages/directories that lead to untraceability and inability to close the loop.
Used when a Spec Pack is completed, reusable assets need to be promoted to the project SSOT (ADR/contract/ops/NFR/registry), and there are risks of "contaminating the project with full package replication / skipping spec-context / mistaking merge-back for git merge".
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.