Loading...
Loading...
Found 54 Skills
OpenSpec Spec-Driven Development Assistant - An AI-aided programming framework based on the OPSX workflow. Align requirements with AI before writing code, and manage changes using a Schema-driven artifact dependency system. Trigger Conditions: 1. User mentions "openspec", "opsx", or spec-driven development 2. User wants to start new feature development or refactoring 3. User needs to explore complex problems or clarify requirements 4. User complains about AI misunderstanding or frequent rework 5. User uses slash commands such as /opsx:new, /opsx:ff, /opsx:apply, etc. 6. During project initialization or preparation for major changes
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 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.
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
Implement approved OpenSpec proposal using DAG-scheduled multi-agent parallel execution
Generate comprehensive OpenSpec specifications directly from the current project state. Use when the user wants to create or populate main specs by analyzing existing code, documentation, AGENTS.md, GitHub issues, and pull requests — without going through the change/proposal workflow. Ideal for bootstrapping specs on a project that already has working code but no specs yet, or for refreshing specs to match the current implementation.
Generate a requirements-quality checklist for an OpenSpec change and run it against the proposal/design/tasks/delta — validating completeness, clarity, consistency, and testability BEFORE you approve the spec. Modeled on GitHub Spec-Kit's /checklist. Use when reviewing a spec at the human approval gate, or before launching implementation, to catch under-specified requirements early.
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.