Loading...
Loading...
Found 1,233 Skills
Use when you need to generate `{FEATURE_DIR}/verification/report-{date}-{version}.md` (test report) during the verification phase of Spec Pack, provide deliverable conclusions that are traceable to test cases and defect references.
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 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/suites.md` (test suite) during the verification phase of Spec Pack, organize test cases into executable sets and define blocking rules and execution order.
Use when you have confirmed the scope of Discover (P0/P1/P2), and now need to quickly build the Level-0 North Star (memory) and Level-1 map layer index skeleton (components/products) under `.aisdlc/project/`, so that you can supplement evidence by module later without double writing and drift.
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.
Used when you need to perform Discover (reverse engineering) on legacy projects with existing code, consolidate repository facts into `.aisdlc/project/`, and you find that AI or teams frequently guess entry points and boundaries, have duplicate writing of indexes and details, or lack evidence chains leading to repeated rework.
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 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.
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.
Used when the current Spec Pack needs to be discarded/revoked due to major requirement issues, and the corresponding `.aisdlc/specs/{branch}` directory as well as local and remote branches must be deleted. Meanwhile, you need to output the deletion list and ask the user for double confirmation before performing the deletion.
Use when you need to turn selected modules (P0 priority first) into single-page module SSOT at the path `.aisdlc/project/components/{module}.md`, and build authoritative entries for API/Data contracts, invariant summaries, evidence entries and structured Evidence Gaps in the same page to meet the DoD gate requirements of Discover.