Loading...
Loading...
Found 48 Skills
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Conversational SDD (Specification-Driven Development) guidance skill based on OpenSpec. It is automatically triggered when a user describes development requirements, and guides the user through the entire SDD process via conversations without any manual command input.
Use this when planning new features, starting spec-driven development workflows, or when the user mentions OpenSpec, SDD, or spec-driven development. It also applies when the user asks about feature specifications, change proposals, or wants to organize development workflows.
Implement approved OpenSpec proposal using DAG-scheduled multi-agent parallel execution
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.
This skill composes project AGENTS.md constitution files into openspec/config.yaml to inject quality validation gates into OpenSpec workflows. Use this skill when initializing openspec for the first time in a project or when AGENTS.md files are updated. The skill ensures openspec artifacts are validated against project-specific quality criteria from constitutions.
Use when you need to take a `*.plan.md` file and turn it into OpenSpec change artifacts by validating OpenSpec installation, initializing or reusing an OpenSpec project, and creating or updating a change proposal/spec/tasks flow. Includes a concrete workflow based on `examples/requirements-examples/problem1/requirements/openspec`. Part of the skills-for-java project
Use when OpenSpec artifacts have been generated by /opsx:propose and need review before implementation begins — validates proposal scope, spec completeness, design decisions, and task executability
Use when the user needs proposal/specs research artifacts produced for a Superspec (superspec-rpi) OpenSpec change.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Author or update the project's constitution — openspec/project.md — the non-negotiable principles, conventions, and constraints the Spec-Driven Development flow must honor. Modeled on GitHub Spec-Kit's /constitution. Run once per repo when onboarding SDD, or whenever the team's principles change. The sdd-feature-flow Analyze gate checks every spec against it.
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.