Loading...
Loading...
Found 56 Skills
Implement a project from its documentation and specification. Use when asked to "implement project", "continue implementation", "build from docs", "implement from spec", or when the user wants to progressively implement a documented project following a todo checklist. Reads docs/, creates implementation plans and todo lists, and implements incrementally with tests and commits.
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Also use when the user wants to break a feature into tasks, plan before coding, track implementation progress, set up a new project structure, or organize work into specs and plans. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive", "break this into tasks", "plan this feature", "start a new project".
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Iteratively review changes, run automated tests, and apply targeted fixes until issues are resolved (or a stop condition is reached).
Automatically loads domain README.md context when you start working in a registered library or module. Reads architecture, public API, and patterns before touching domain-specific code. Activate when the task involves a specific library, domain path, or module the user references.
Use when starting a new project, adding a major feature to an existing system, or when unsure which skills to run and in what order. Supports macOS, iOS, web, full-stack, voice agent, and edge/IoT+ML projects.
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.
Archive completed plans from plans/active/ to plans/completed/, supplement verification results and completion time. Suitable for calling after implementation is finished.
Bence's code style, tech stack, and workflow conventions
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, batched graph sync, and scoped reviews.
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.
Assess if IDD fits your project and learn about Intent-Driven Development. Use /intent-assess to evaluate project suitability or /intent-assess --learn for IDD education.