Loading...
Loading...
Found 68 Skills
Discuss and brainstorm a spec-driven change from a rough idea, then propose a change name and, after explicit confirmation, generate the same five proposal artifacts as spec-driven-propose.
Modify an existing spec-driven change artifact (proposal.md, specs/ delta files, design.md, tasks.md, or questions.md). Preserves completed task state.
Meta-prompting, context engineering, and spec-driven development system for autonomous long-running coding agents
Recommend the next roadmap-backed change, then after explicit confirmation scaffold it as a normal spec-driven change.
Extract formal spec and comprehensive test suites from existing MoonBit implementations. Use when asked to "extract spec from implementation", "generate tests from code", or "create spec-driven tests for existing package". Analyzes existing code to produce spec.mbt with `declare` keyword stubs and organized test files (valid/invalid).
Disciplined spec-driven test-driven development workflow for building software with AI coding agents. Transforms ambiguous requests into verified implementations through structured specification, test derivation, and strict TDD. Handles greenfield projects, brownfield enhancements (with or without existing tests), refactors, and complex bug fixes with workflow-specific guidance for each. Use when the user requests a new feature, module, enhancement, refactor, API, data pipeline, CLI tool, or system with multiple requirements, edge cases, or unclear specifications. Also use for complex bug fixes requiring root cause analysis. Triggers on phrases like "add a feature", "implement", "build a new module", "build an API", "build a CLI", "build a data pipeline", "refactor", "fix this bug", "write tests for", "TDD", "test-first", "the requirements are unclear", "characterization tests", or "spec this out". Triggers when modifying code with adjacent test files (`tests/`, `*_test.py`, `*.test.ts`, `*.spec.ts`, `spec/`, `__tests__/`) or test framework config (pytest.ini, jest.config.*, go.mod with testing imports, Cargo.toml with [dev-dependencies], package.json with a test script). Triggers when the user mentions edge cases, invariants, acceptance criteria, EARS notation, or red-green-refactor. Do NOT use for simple one-line fixes, cosmetic changes, formatting, renames, dependency bumps, or tasks where requirements are already fully specified with tests provided.
Bootstrap the openspec/ directory structure for Spec-Driven Development in any project. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
Initialize Spec-Driven Development context — detects tech stack, conventions, architecture patterns, and bootstraps persistence backends. Triggers on 'sdd-init', 'init sdd', 'setup sdd', 'initialize sdd', 'setup project', 'initialize project context'. Creates/updates docs/specs/architecture.md & ontology.md (Constitution), and populates knowledge-graph.json.
Practice spec-driven development with Momentic browser tests. Use when implementing new user-visible functionality or changing existing behavior in a repository with Momentic tests, especially when the user asks to write or update the affected *.test.yaml specifications before changing product code.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Spec-driven development pipeline orchestrator. Given a URL or text description, automatically generates specs, implements code, runs codex review, applies security gate, executes tests, syncs docs, and notifies via Telegram. Triggers on: /start-workflow, start workflow, build feature, implement feature, spec-driven, start pipeline.
Run the full spec-driven workflow automatically. Proposes, implements, verifies, reviews, and archives a change with one mandatory proposal checkpoint plus any extra confirmations required by blocking conditions.