Loading...
Loading...
Found 56 Skills
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.
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".
Interactive onboarding workflow that interviews users to understand their coding goals and generates PR-ready implementation plans. Use when starting a new development task to ensure clear requirements and structured execution.
CX Workflow - Task Execution and Contract Validation. Triggered when users mention phrases such as "execute task", "start development", "implement feature", "write code", "continue working", "next task". It follows a 5-step process: Read Task → Implementation → Contract Validation → Testing → Submission. It uses local task-{n}.md and status.json files to automatically verify whether the implementation conforms to the contract. cx-summary will be automatically triggered after all tasks are completed.
Use when implementing features from a spec or requirements document, doing multi-phase work, or when you need structured Analyze-Plan-Ask-Execute-Review cycles to prevent ad-hoc coding and ensure spec-aligned, pattern-consistent implementations