Loading...
Loading...
Found 52 Skills
Design and execute tests for an approved DevFlow Spec only when explicitly invoked by the user or precisely delegated by the Planner; maintain an acceptance traceability matrix; complete feature, contract, integration, E2E, regression, and real-scenario verification; output a test report and defect evidence bound to the Commit SHA; do not modify production code.
Add traceability columns to a spreadsheet source and write created Azure DevOps ticket IDs/URLs back into it, matched row-by-row by key. Use this right after creating work items — when you have a backlog_result.json and the original source was a spreadsheet (xlsx/csv). Triggers on "write the ticket links back", "track which row got which ticket", "update the spreadsheet with the ADO IDs", "fill in the ticket column", "close the loop on the audit sheet", or any request to record created-item IDs back onto the source rows. Runs the bundled tracking.py (add-columns + writeback). For doc/pasted-text input there are no rows to write to — in that case just report the created links instead.
Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC **product half** (capability closure satisfied) with Closes #N traceability.
Add traceability columns to a spreadsheet source and write created GitHub issue numbers/URLs back into it, matched row-by-row by key. Use this right after creating issues — when you have a github_backlog_result.json and the original source was a spreadsheet (xlsx/csv). Triggers on "write the issue links back", "track which row got which issue", "update the spreadsheet with the GitHub IDs", "fill in the issue column", "close the loop on the audit sheet".
Create Business Requirements Documents (BRD) following SDD methodology - Layer 1 artifact defining business needs and objectives
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Design test cases based on requirements. Use when users need test case design, testing strategy, or QA planning. Triggers on keywords like "test cases", "test design", "unit test", "integration test", "e2e test".
Create Atomic Requirements (REQ) - Layer 7 artifact using REQ v3.0 format with 12 sections, SPEC-readiness scoring, and IMPL-readiness scoring
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
Systematically collect, document, and validate requirements from stakeholders. Ensure clarity, completeness, and agreement before development begins to reduce scope creep and rework.
AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology
Layer 4 artifact for Behavior-Driven Development test scenarios using Gherkin Given-When-Then format