The OpenSpec-Siraj pipeline overview. Canonical orchestrator for the siraj-openspec- family of skills (create-design, create-plan, review-change, stress-test-tasks, stress-test-plan, execute-plan) plus the /siraj-openspec: CLI commands (new, verify, archive, sync, etc.). Use this skill to orient on the full pipeline (proposal → spec → design → tasks → per-commit plans → execution → verify → archive), to figure out which verb fires next given an OpenSpec change folder's current state, or as the canonical reference for numbering, scenario titles, cross-file references, renumbering, tasks.md commit-block shape, and artifact-tree conventions. Trigger on phrasing like "what's the openspec workflow", "where am I in this change", "walk me through the openspec pipeline", "start a new openspec change", "how do I author tasks.md", or whenever the user pauses on an openspec/changes/ / folder and asks what's next. For lightweight greenfield app/feature builds use feather-flow instead; the two are peer pipelines, not variants. Defaults to the most-recently-modified change folder if no name is given.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryDeveloper toolsStars0
About this skill
The OpenSpec-Siraj pipeline overview. Canonical orchestrator for the siraj-openspec- family of skills (create-design, create-plan, review-change, stress-test-tasks, stress-test-plan, execute-plan) plus the /siraj-openspec: CLI commands (new, verify, archive, sync, etc.). Use this skill to orient on the full pipeline (proposal → spec → design → tasks → per-commit plans → execution → verify → archive), to figure out which verb fires next given an OpenSpec change folder's current state, or as the canonical reference for numbering, scenario titles, cross-file references, renumbering, tasks.md commit-block shape, and artifact-tree conventions. Trigger on phrasing like "what's the openspec workflow", "where am I in this change", "walk me through the openspec pipeline", "start a new openspec change", "how do I author tasks.md", or whenever the user pauses on an openspec/changes/ / folder and asks what's next. For lightweight greenfield app/feature builds use feather-flow instead; the two are peer pipelines, not variants. Defaults to the most-recently-modified change folder if no name is given.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
The OpenSpec-Siraj pipeline overview. Canonical orchestrator for the siraj-openspec-* family of skills (create-design, create-plan, review-change, stress-test-tasks, stress-test-plan, execute-plan) plus the /siraj-openspec:* CLI commands (new, verify, archive, sync, etc.). Use this skill to orient on the full pipeline (proposal → spec → design → tasks → per-commit plans → execution → verify → archive), to figure out which verb fires next given an OpenSpec change folder's current state, or as the canonical reference for numbering, scenario titles, cross-file references, renumbering, tasks.md commit-block shape, and artifact-tree conventions. Trigger on phrasing like "what's the openspec workflow", "where am I in this change", "walk me through the openspec pipeline", "start a new openspec change", "how do I author tasks.md", or whenever the user pauses on an openspec/changes/<X>/ folder and asks what's next. For lightweight greenfield app/feature builds use feather-flow instead; the two are peer pipelines, not variants. Defaults to the most-recently-modified change folder if no name is given.
About this listing
Category
Developer tools
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.