Openspecpm

OpenSpecPM — Spec-driven PM Agent Skill

A sibling of CCPM with five differences: OpenSpec authors the specs (with a heuristic BDD linter plus an optional LLM judge), adapters make the PM backend pluggable (GitHub / Azure DevOps / Jira / Linear / GitLab), the wizard is friendly to non-engineers, every command is audit-logged by default, and depends_on: reaches across features so next/blocked reflect the whole project.

Workflow

idea → openspecpm propose            (OpenSpec authors proposal.md, design.md, tasks.md, specs/)
     → review BDD scenarios                   (Given/When/Then)
     → openspecpm sync               (push to chosen PM backend, idempotent)
     → openspecpm status / standup            (track local + remote)
     → openspecpm ship               (close + archive)

Phases

| Phase | When to read | Reference | |---|---|---| | Plan | User wants to define a new feature with BDD scenarios. | references/plan.md | | Structure | A proposal exists and needs decomposition into tasks. | references/structure.md | | Sync | Local OpenSpec change needs to become PM-tool work items. | references/sync.md | | Execute | User wants to start work on a tracked item. | references/execute.md | | Track | User asks status / standup / what's next / what's blocked. | references/track.md |

Conventions

Before any work, read [references/conventions.md](references/conventions.md) for file paths, frontmatter schemas, and BDD format rules.

Script-first rule

Deterministic operations run through the Node CLI directly — same shape as CCPM's bash scripts, but cross-platform:

| What the user wants | Command | |---|---| | First-time setup | npx openspecpm init | | Auth health check | npx openspecpm doctor | | Install missing tooling hints | npx openspecpm doctor --install | | PAT/token creation hints | npx openspecpm doctor --setup-auth | | Create a proposal | npx openspecpm propose [--llm] | | Decompose proposal → tasks | npx openspecpm decompose | | Push to PM tool | npx openspecpm sync [--llm] | | Push every change at once | npx openspecpm sync --all | | Broadcast progress | npx openspecpm comment | | Pull remote state back | npx openspecpm reconcile | | Assign / sprint / story-points | npx openspecpm assign [--assignee X] [--sprint Y] | | File a regression | npx openspecpm bug-report --title "..." | | Status snapshot | npx openspecpm status | | Standup digest | npx openspecpm standup | | What to work on next | npx openspecpm next | | What's blocked | npx openspecpm blocked | | Validate everything | npx openspecpm validate [--llm] | | Re-lint on file change | npx openspecpm watch [feature] | | Search across changes | npx openspecpm search | | Fan-out parallel agents | npx openspecpm fan-out | | Close + archive | npx openspecpm ship | | Ship every ready change | npx openspecpm ship --all-ready | | Phase-grouped help | npx openspecpm help-table |

Every command writes an audit entry to .openspecpm/audit.log (JSONL, secrets scrubbed).

Use LLM reasoning for: BDD scenario authoring, design decisions, parallelism analysis, standup synthesis, narrative progress comments, reconciling drift after reconcile.

Disambiguation vs CCPM

This skill and ccpm overlap intentionally. Routing rules:

• User says "OpenSpec", "BDD", "Given/When/Then", "Jira", "Azure DevOps", or names a non-GitHub backend → openspecpm.
• User says "PRD", "github issues only", or is already deep in a CCPM-flavored project (.claude/prds/ exists) → ccpm.
• Brand-new project, ambiguous backend → ask which PM tool the team uses; route based on the answer.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: aks-builds
• Source: aks-builds/openspecpm
• License: MIT
• Homepage: https://www.npmjs.com/package/openspecpm

Install and usage instructions live in the source repository linked above.