Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/CODEOWNERS. Use when setting up triage automation on a new or existing repository for the first time.
Generate a local static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Compare a pull request's implementation against spec context in speccontext.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Create a product spec from a GitHub issue in this repository by applying the local shared write-product-spec workflow with issue context and output paths. Use when an issue should be turned into a product spec artifact stored under specs/issue- /product.md and the agent should prepare file changes only, without…
Create a technical spec from a GitHub issue in this repository by applying the local shared write-tech-spec workflow with issue context and output paths. Use when an issue should be turned into a tech spec artifact stored under specs/issue- /tech.md and the agent should prepare file changes only, without creating…
Implement a GitHub issue in this repository by applying the local shared implement-specs workflow with repository-specific issue, spec-context, and summary-file handling. Use when issue details are provided in the prompt and the agent should produce the implementation diff and handoff metadata without creating pull…
Implement an approved feature from the repository's product and tech specs, keeping specs and code aligned in the same change as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.