Loading...
Loading...
Found 44 Skills
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Generate comprehensive documentation with intelligent orchestration and parallel execution
Specification-driven implementation — Execute implementation from specs to PR. Reads issue-to-pr-workflow.md as playbook, enforces coding-rules.md as quality gates, tracks progress via tasks.md checkboxes with resume capability. English triggers: "Implement from spec", "Start implementation", "Execute spec tasks" 日本語トリガー: 「仕様書から実装」「実装を開始」「specタスクを実行」
Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop
Create install.md files optimized for AI agent execution. Use for ANY question about install.md files or request to create/review installation documentation for autonomous agent use.
Create work-order with minimal context for isolated subagent execution, optionally linked to GitHub issue
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
Runs .continue/agents checks locally against the current diff, simulating the GitHub PR checks experience. Use when the user says /check to review their changes before pushing.
Generate a pack of professional or aesthetic photos from a single reference image while preserving the exact identity of the person.
Use when a task has multiple independent subtasks that can be executed concurrently by separate agents. Triggers when decomposed work has 2+ subtasks with no data dependencies, when subtasks operate on different files or codebase sections, when serial execution time would be significantly longer than parallel, or when independent analyses or deliverables need concurrent generation.
Create and run durable workflows with steps, streaming, and agent execution. Covers starting, resuming, and persisting workflow results.