Split tracked design specs into GitHub issue epics and child queues.
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-split
Please help me install this Agent Skill. Skill: autospec-split Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-split Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-split
Autospec-split turns an already-written, tracked design spec in docs/specs into a properly labeled GitHub issue epic plus an auto-implement child-issue queue, so you can start implementation without rewriting planning.
Ask your agent to split an existing spec into issues and stop for the /autospec-run handoff by requesting: split latest spec.
High-intent search queries and answers about installing and using this skill.
To decompose an existing markdown spec into GitHub issues, use autospec-split. It resolves a tracked design doc in docs/specs/*.md and generates a linked epic umbrella issue plus self-contained child issues ready for execution without rewriting your planning.
Spec decomposition does not require writing a new design document. The process selects an already-written tracked design spec from docs/specs and skips the brainstorming phase, directly converting your existing product intent into an auto-implement issue queue.
You generate a GitHub issue queue with deterministic labels by running controlled issue generation via the GH CLI. The workflow applies model-fit labeling and lint gates to produce an epic plus N linked child issues ready for local-LLM execution.
To decompose specs and create GitHub epics, you need curl, gh, jq, and git installed. These command-line dependencies handle repo validation, origin/main tracking checks, and controlled GitHub issue generation.
You can use autospec-split to create issues for local-LLM execution and stop before coding. The workflow halts after Phase 3.5 with a handoff step, allowing implementation to begin immediately without writing any code during the decomposition phase.
When multiple design specs exist in the docs/specs directory, the workflow performs candidate-spec resolution with ambiguity prompting. You can provide an explicit path to select the correct file or let the system target the newest candidate spec automatically.
team-attentionGenerate a Draft PR from a validated spec using a PR body template.
berlinguyincaApply Phase 3.5 ctx and reasoning labels to GitHub auto-implement issues.
berlinguyincaSupervise autospec execution across GitHub repositories with queue summaries.
jarrett-auDecompose large project requirements into GitHub issues with dependencies.
