openspec-dev

Convert OpenSpec change proposals into phase-based plans and PR workflows.

4|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/akornmeier/claude-config --skill openspec-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-dev
Source: https://github.com/akornmeier/claude-config/tree/main/skills/openspec-dev
Command: npx skills add https://github.com/akornmeier/claude-config --skill openspec-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill transforms OpenSpec change proposals into actionable execution plans by phase, enabling structured, phased development and clear PR ownership.

Core Features & Use Cases

  • Phase-based planning: groups tasks by phases and builds per-phase execution plans.
  • Automated PR orchestration: creates phase-specific branches and PRs with context.
  • Workflow integration: coordinates with subagent-driven-development and TDD tooling for reliable delivery.

Quick Start

Invoke the skill with a change identifier to generate the phased plan and PRs, for example: /openspec-dev add-launch-features

Frequently Asked Questions about openspec-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate phase-driven development and PR creation from task lists?

You can automate phase-driven development by grouping tasks from tasks.md into phases, generating phase-specific git branches, and creating GitHub PRs automatically as each phase progresses. This converts change proposals into executable phase-based workflows.

What is phase filtering in git workflow automation?

Phase filtering in git workflow automation groups tasks by phase from tasks.md, enforcing sequential execution and creating phase-specific branches. It ensures PRs are organized by development phase, preventing tasks from later phases from mixing into earlier ones.

How do I convert OpenSpec change proposals into executable plans?

Converting OpenSpec change proposals into executable plans involves grouping tasks by phase from tasks.md, building per-phase execution plans, and orchestrating phase-specific PR creation to structure development with clear ownership.

Can I integrate phase-based task management with GitHub PR workflows?

Yes, phase-based task management integrates with GitHub PR workflows by creating phase-specific branches and PRs with context. The skill coordinates PR creation and updates the source tasks.md as progress is made through each phase.

Does phase-driven PR automation work with subagent-driven development and TDD tooling?

Phase-driven PR automation coordinates with subagent-driven development and TDD tooling for reliable delivery. It structures work into phased execution plans that align with these development methodologies.

Why group git branches by phase instead of feature for task-management?

Grouping git branches by phase enforces sequential execution and clear PR ownership, ensuring tasks.md updates reflect incremental progress. This prevents overlapping changes and maintains structured delivery across complex change proposals.