Loading...
Loading...
Found 66 Skills
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
Effective communication strategies for AI-assisted development. Learn context-first prompting, phased interactions, iterative refinement, and validation techniques to get better results from Claude and other AI coding assistants.
Meta-prompting, context engineering, and spec-driven development system for autonomous long-running coding agents
Verify a spec-driven change is complete and correctly implemented. Checks task completion, implementation evidence, and spec alignment.
Recommend the next roadmap-backed change, then after explicit confirmation scaffold it as a normal spec-driven change.
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 ready to implement designed features - breaks design into TDD tasks (Red-Green-Refactor), tracks progress with checkboxes in tasks.md, enforces strict testing discipline. Activates when user says "implement this", "let's code", "start execution", mentions "tasks", "TDD", or uses /dev-workflow:spec commands (tasks, execute).
Guide spec-driven feature development using a structured three-phase workflow: Requirements → Design → Tasks. Use this skill whenever the user wants to plan a feature, write a spec, or do structured design before coding. Trigger on phrases like "let's spec this out", "write a specification" or "help me think through this feature".
Retrofit or repair spec frontmatter mappings between specs, implementation files, and test files.
Initialize the .specify/ directory structure for Spec-Driven Development in the current project
Use when the user wants to set up spec-driven development (OpenSpec + superpowers-bridge) in a project, or when initializing a new project that needs the SDD workflow. Idempotent. Runs the bundled scripts/run.sh.
Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.