← ClaudeAtlas

planlisted

Epic decomposition into trackable issues. Triggers: "create a plan", "plan implementation", "break down into tasks", "decompose into features", "create beads issues from research", "what issues should we create", "plan out the work".
boshu2/agentops · ★ 369 · AI & Automation · score 80
Install: claude install-skill boshu2/agentops
# Plan Skill > **Quick Ref:** Decompose goal into trackable issues with waves. Output: `.agents/plans/*.md` + bd issues. **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** ## Flags | Flag | Default | Description | |------|---------|-------------| | `--auto` | off | Skip human approval gate. Used by `$rpi --auto` for fully autonomous lifecycle. | | `--fast-path` | off | Force Minimal detail template (see Step 3.2) | ## Execution Steps Given `$plan <goal> [--auto]`: ### Step 1: Setup ```bash mkdir -p .agents/plans ``` ### Step 2: Check for Prior Research Look for existing research on this topic: ```bash ls -la .agents/research/ 2>/dev/null | head -10 ``` Use Grep to search `.agents/` for related content. If research exists, read it to understand the context before planning. **Search knowledge flywheel for prior planning patterns:** ```bash if command -v ao &>/dev/null; then ao search "<topic> plan decomposition patterns" 2>/dev/null | head -10 ao lookup --query "<goal>" --limit 5 2>/dev/null | head -30 fi ``` **Apply retrieved knowledge (mandatory when results returned):** If ao returns relevant learnings or patterns, do NOT just load them as passive context. For each returned item: 1. Check: does this learning apply to the current planning goal? (answer yes/no) 2. If yes: incorporate as a planning constraint — does it warn about scope? suggest decomposition? flag a known pitfall? 3. Cite applicable learnings by filename when they influence a plan