Autonomous planning — reads issue and design, posts implementation plan, never blocks.
Break an approved design into implementation tasks without user interaction. This is the worktree variant of design_plan.
Rule: no implementation until a plan is posted. No blocking for feedback.
git branch --show-current<type>/<issue_number>-<summary> (e.g. feature/79-declarative-sync-manifest). See branch-naming.mdc for the full convention.<issue_number> from the branch name.gh issue view <issue_number> --json title,body,labels,comments
## Design comment for the approved architecture.## Implementation Plan comment already exists, skip — the planning phase is done.## Design comment exists, invoke worktree_brainstorm first.just test, specific test passes).Determine the repo: gh repo view --json nameWithOwner --jq '.nameWithOwner'
Post the plan comment:
gh api repos/{owner}/{repo}/issues/{issue_number}/comments \
-f body="<plan_content>"
The comment must start with ## Implementation Plan (H2) — this is how other skills detect that the planning phase is complete.
Use this format:
## Implementation Plan
Issue: #<issue_number>
Branch: <branch_name>
### Tasks
- [ ] Task 1: description — `files` — verify: `command`
- [ ] Task 2: description — `files` — verify: `command`
...
The following steps SHOULD be delegated to reduce token consumption:
model: "fast" that validates the branch name, executes gh issue view, checks for existing ## Design and ## Implementation Plan comments. Returns: issue number, parsed body/design, plan-exists flag.model: "fast" that takes the formatted plan content and posts it via gh api. Returns: comment URL.Step 2 (break into tasks) should remain in the main agent as it requires task decomposition and dependency analysis.
Reference: subagent-delegation rule