Generate sprint stories from epic registry dependencies and research-backed specs.
npx skills add https://github.com/lasswellt/claudeHQ --skill sprint-plan-lasswellt
Please help me install this Agent Skill. Skill: sprint-plan Source: https://github.com/lasswellt/claudeHQ/tree/main/.claude/skills/sprint-plan Command: npx skills add https://github.com/lasswellt/claudeHQ --skill sprint-plan-lasswellt
Planning and generating sprint stories for claudeHQ requires manual coordination of epics, dependencies, and research. This skill automates the process end-to-end by reading the epic registry, performing a topological sort, selecting the next unblocked batch, and spawning research agents to produce implementation stories with vetted specs.
Execute the sprint planning workflow to generate a new sprint plan and associated stories.
High-intent search queries and answers about installing and using this skill.
Automate sprint planning by reading the epic registry, sorting dependencies topologically, selecting unblocked epics, and spawning research agents to generate ready-to-implement stories with concise specs.
Generate implementation stories by performing a topological sort on your dependency graph, selecting the next unblocked batch of epics, and spawning research agents to produce vetted specifications automatically.
Autonomous sprint planning reads epic registry data and dependency graphs, sorts epics topologically to find unblocked work, and spawns research agents to produce implementation stories with vetted specs.
Yes, you can create a sprint draft automatically by reading the epic registry, performing a topological sort on dependencies, selecting unblocked epics, and generating implementation stories with research-backed specifications.
You need an epic registry with defined dependencies and research-backed specs. The skill reads this registry data, sorts by dependencies, and outputs ready-to-implement stories with concise specs and references.
Avoid automated sprint planning if your epics lack defined dependencies or research-backed specifications, as the workflow relies on reading registry data and dependency graphs to output ready-to-implement stories.
adamaltmejdParse GitHub issue labels and dependencies to generate structured project roadmaps.
djnsty23Summarize sprint progress and task status from prd.json sprint data.
amitmishra-bylddExecute story implementation from context-filled spec files with status transitions.
firefly-eventsCoordinate multi-agent Epic execution by loading config and running stories in dependency order.
