openspec-dev

• Active OpenSpec change with approved proposal.md
• Populated tasks.md with tasks organized by phase
• Clean git state on main branch

```

/openspec-dev [phases]

```

Arguments:

• — Required. The OpenSpec change directory name
• [phases] — Optional. Phase filter using numeric ranges (e.g., 1,3,5-7)

Examples:

• /openspec-dev add-launch-features — Execute all phases
• /openspec-dev add-launch-features 2 — Execute phase 2 only
• /openspec-dev add-launch-features 1,3-5 — Execute phases 1, 3, 4, and 5

---

When [phases] is provided, only matching phases from tasks.md are executed.

Parsing rules:

• Single number: 2 → phase 2 only
• Comma-separated: 1,3,5 → phases 1, 3, and 5
• Range with dash: 2-4 → phases 2, 3, and 4
• Mixed: 1,3-5,7 → phases 1, 3, 4, 5, and 7
• Whitespace ignored, duplicates removed, sorted ascending

Phase numbering: Phases are numbered by order in tasks.md (first ## Phase ... = 1, second = 2, etc.)

Error handling:

• Invalid phase number (doesn't exist): Warn and skip, continue with valid phases
• Phase already complete (all tasks checked): Log "Phase N: No unchecked tasks, skipping"
• Malformed input (non-numeric, zero, negative): Error with usage example

---

```

Parse OpenSpec → Extract phases → Per phase: branch + subagent-driven-dev + PR

```

---

Read and extract from openspec/changes//:

1. proposal.md — identify phases/milestones
2. tasks.md — extract tasks, group by phase
3. Apply phase filter (if [phases] provided):

- Parse phase numbers from argument

- Filter to only matching phases

- Warn for non-existent phases

- Log and skip phases with no unchecked tasks

```markdown

# Example tasks.md structure

• [ ] Add user authentication endpoint
• [ ] Create data validation layer

• [ ] Build login form component
• [ ] Add dashboard layout

```

Extract unchecked tasks (- [ ]) grouped by their phase heading. When [phases] is specified, only process matching phases.

---

For each phase with unchecked tasks:

2a. Create Phase Branch

```bash

git checkout main && git pull

git checkout -b feat/-phase-N

```

2b. Prepare Plan for Subagent-Driven-Development

Convert phase tasks into a plan format:

```markdown

# Phase N:

OpenSpec change:

Spec reference: openspec/specs//spec.md

...

```

2c. Invoke Subagent-Driven-Development

Follow the superpowers:subagent-driven-development workflow:

• Dispatch implementer subagent per task (sequential)
• Two-stage review: spec compliance → code quality
• Use TDD discipline throughout

The subagent-driven-development skill handles:

• Implementer prompts and self-review
• Spec compliance review
• Code quality review
• Retry loops for issues

2d. Create PR for Phase

When all phase tasks complete:

```bash

gh pr create \

--title "feat(): Phase N - " \

--body "## Summary

• Change: openspec/changes//proposal.md
• Tasks: Phase N from tasks.md

"

```

---

Critical: Keep openspec/changes//tasks.md updated as the source of truth.

After Each Task Completes

When a task passes both reviews in subagent-driven-development:

1. Update the source file openspec/changes//tasks.md
2. Change - [ ] to - [x] for the completed task
3. Commit the update to the phase branch

```bash

# Example: mark task complete in source file

# In openspec/changes/add-launch-features/tasks.md:

# - [ ] Add user authentication endpoint → - [x] Add user authentication endpoint

git add openspec/changes//tasks.md

git commit -m "chore(openspec): mark task complete - "

```

After Phase PR Created

Add PR reference to completed tasks:

```markdown

• [x] Add user authentication endpoint (PR #142)
• [x] Create data validation layer (PR #142)

```

Why This Matters

• Resumability: If execution stops mid-phase, progress isn't lost
• Visibility: Anyone can check tasks.md to see current status
• Idempotency: Re-running the skill skips already-completed tasks (- [x])

---

After all phases:

```markdown

| Phase | Branch | PR | Status |

|-------|--------|-----|--------|

| Phase 1: Core API | feat/change-id-phase-1 | #142 | Ready |

| Phase 2: UI Components | — | — | Skipped (not in filter) |

| Phase 3: Tests | — | — | Skipped (already complete) |

| Phase 4: Docs | feat/change-id-phase-4 | #143 | Ready |

Next Steps

• Review and merge PRs in phase order
• Run again if tasks were added or skipped

```

Status values:

• Ready — PR created, awaiting review
• Skipped (not in filter) — Phase excluded by [phases] argument
• Skipped (already complete) — All tasks in phase already checked

---

This skill is a thin adapter that delegates to:

| Skill | Purpose |

|-------|---------|

| superpowers:subagent-driven-development | Task execution, reviews, retry loops |

| superpowers:test-driven-development | TDD discipline (used by implementers) |

| superpowers:finishing-a-development-branch | Final cleanup if needed |

Do not duplicate the implementation/review logic from subagent-driven-development.