← ClaudeAtlas

openspecpmlisted

OpenSpecPM — spec-driven, BDD-shaped project management for any PM backend: OpenSpec proposal → BDD specs (Given/When/Then) → tasks → GitHub Issues / Azure DevOps Boards / Jira / Linear / GitLab → shipped code. Use this skill when the user wants to (a) author a proposal with rigorous BDD scenarios ('write a proposal for X', 'spec out X', 'turn this into Given/When/Then'), (b) decompose a proposal into tasks ('break down the X proposal', 'split this into work items'), (c) sync work to a PM backend ('push X to GitHub', 'sync the X epic to Jira', 'create work items in Azure DevOps', 'push to Linear', 'create GitLab issues'), (d) broadcast progress or reconcile drift ('post my update on task Y', 'pull remote state back', 'reconcile the X feature'), (e) check progress ('status', 'standup', 'what should I work on next', 'what's blocked', 'validate', 'search the proposals for Z'), (f) coordinate parallel work ('fan out the X epic', 'dispatch parallel agents'), (g) assign or schedule synced work ('assign task Y to Z'
aks-builds/openspecpm · ★ 1 · Testing & QA · score 67
Install: claude install-skill aks-builds/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 <feature> (OpenSpec authors proposal.md, design.md, tasks.md, specs/) → review BDD scenarios (Given/When/Then) → openspecpm sync <feature> (push to chosen PM backend, idempotent) → openspecpm status / standup (track local + remote) → openspecpm ship <feature> (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) fo