Loading...
Loading...
Found 147 Skills
Use this when you have a written implementation plan to execute in a separate session with review checkpoints.
Core software engineering principles for code style, documentation, and development workflow. Applies when editing code, working in software repositories, or performing software development tasks.
Bounded codebase exploration and architecture mapping. Use when discovery is needed before implementation. Do NOT use for broad refactoring — use do-plan instead.
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format
Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of engineering makes subsequent work easier. Triggers on: plan this feature, implement this, review this code, compound learnings, create implementation plan, systematic development.
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.
Agent development workflow and discipline skills. Use when developing features, debugging issues, managing code branches, writing plans, or ensuring code quality through TDD and systematic processes. Triggers on any software development task that benefits from structured workflows.
Use when executing multi-task plans where each task can be implemented independently by a subagent. Triggers when a plan has 3+ independent tasks, when speed of execution is important, when tasks have clear acceptance criteria suitable for delegation, or when two-stage review gates (spec compliance and code quality) are needed for iterative fix cycles.
After implementation is complete and tests pass, sync confirmed details back to Intent. Captures finalized interfaces, data structures, naming conventions, and architecture decisions. Use after development is done and user confirms the implementation.
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.