Loading...
Loading...
Found 58 Skills
Bug-to-test pipeline: reproduce the bug as a failing test first, then fix. The regression test lives forever.
Used to confirm that development is completed and ensure all tests/checks have passed
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.
MCP Status
Use when asked to fix, resolve, or address a GitHub PR — including review comments, Copilot suggestions, and CI test failures. Triggers on phrases like "fix PR", "fix PR comments", "resolve review", "address Copilot feedback", "fix review comments", "fix CI", "fix failing tests on PR", or when given a PR number to fix.
Implement a project from its documentation and specification. Use when asked to "implement project", "continue implementation", "build from docs", "implement from spec", or when the user wants to progressively implement a documented project following a todo checklist. Reads docs/, creates implementation plans and todo lists, and implements incrementally with tests and commits.
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.
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Make all tech decisions, write CLAUDE.md, scaffold the project, and get a smoke test passing. Run after /wireframe.
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 completing tasks, implementing major features, or before merging to verify work meets requirements
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.