jupes/agent-forge-harness / .agents/skills/to-issues
to-issues
VerifiedDecompose a plan or PRD into independently verifiable Beads tasks with dependencies. Use when turning agreed scope into executable issues.
to-issues
Convert a plan, PRD, or feature brief into small, independently executable Beads tasks.
Process
1) Gather source context
Use available material first:
- Conversation context
- PRD/plan text
- Existing bead (
bd show <id>) - Relevant codebase context
If user provides an external issue/URL, map it into local context before decomposition.
2) Draft tracer-bullet vertical slices
Each slice must be an end-to-end path through relevant layers (contract, logic, integration, verification), not a single-layer chunk.
Rules:
- Demoable/verifiable on its own
- Prefer many thin slices over few large slices
- Minimize cross-slice coupling
- Mark slices as:
AFK: can execute without user interventionHITL: requires human decision/review checkpoint
3) Review slice plan with user
Present a numbered list with:
- Title
- Type (
AFK/HITL) - Blocked by (if any)
- User stories covered (if source has stories)
Refine until approved.
4) Create Beads issues
Create issues in dependency order so blockers exist first.
Use this issue body format:
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Blocked by
- None - can start immediately or
Notes
- Type: AFK/HITL
- Risks or assumptions
Commands:
Choose priority with beads-priority-assignment before creating work. Reuse an existing issue when it already owns the outcome.
bd create --type task --title "<slice title>" --description "<template markdown>" --priority <priority> --repo .
bd dep add <blocked-id> <slice-id> # the blocked issue first: it depends on the slice that blocks it
If slices derive from a parent PRD/feature, attach children:
bd create --type task --parent <parent-id> --title "<slice title>" --description "<template markdown>" --priority <priority> --repo .
5) Validate and report
- Verify dependency graph (
bd children <parent-id>and/orbd graph) - Confirm no orphaned critical-path work
- Add
worklog:comment to parent summarizing decomposition decisions
Completion
Every in-scope outcome maps to a verifiable task; created IDs and parent links resolve, dependencies have no cycles, and deferred scope has an explicit disposition.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |