implement-spec
Orchestrate implementation of spec-workflow tasks. Use when user says "implement the spec", "execute spec tasks", "run the spec workflow", "implement spec-name tasks", or needs to coordinate agent execution for spec-workflow documents.
What this skill does
# Implement Spec Orchestrate implementation of spec-workflow tasks using intelligent agent coordination, parallel execution, and quality gates. ## When to Activate - User wants to implement spec-workflow tasks - Spec documents exist in `.spec-workflow/specs/` - User asks to "execute the spec" or "implement spec tasks" - Coordinated multi-agent task execution is needed ## Inputs Parse from request: - **spec-name**: Name of the spec to implement from `.spec-workflow/specs/` - **--task**: Specific task ID to implement (optional, defaults to next pending) - **--parallel**: Enable parallel execution of independent tasks - **--dry-run**: Preview the orchestration plan without executing - **--quality-gates**: Enable quality checks between phases (default: true) ## Quick Process 1. **Load Spec Context**: Retrieve requirements, design, and tasks from spec-workflow 2. **Task Analysis**: Decompose tasks and identify dependencies 3. **Agent Selection**: Match tasks to specialized agents based on capabilities 4. **Execution Orchestration**: Coordinate parallel/sequential execution 5. **Quality Assurance**: Validate outputs and ensure consistency ## Orchestration Strategy ### Phase 1: Context & Planning 1. **Spec Loading**: - Use `mcp__spec-workflow__get-spec-context` to load spec documents - Use `mcp__spec-workflow__manage-tasks` to get task status - Identify pending tasks and dependencies 2. **Dependency Analysis**: - Map task dependencies from the tasks.md structure - Identify parallel execution opportunities - Determine critical path for sequential tasks ### Phase 2: Agent Orchestration **If agent-orchestrator-agent is available** (from development-codebase-tools plugin): Invoke it with comprehensive context including: - Loaded specs and pending tasks - Task dependencies - Execution strategy (parallel vs sequential) The orchestrator will: - Discover all available agents - Use **agent-capability-analyst** for optimal matching - Coordinate specialized agents for each task - Handle parallel execution groups **Fallback (if agent-orchestrator-agent is not available)**: Execute tasks sequentially without orchestration: 1. Process tasks in dependency order from tasks.md 2. For each task, directly invoke the most appropriate available agent 3. Pass task context and previous results to each agent 4. Continue until all tasks are complete or a blocker is encountered ### Phase 3: Task Execution For each task, coordinate: 1. **Code Implementation Tasks**: code-generator-agent, test-writer-agent, documentation-agent 2. **Refactoring Tasks**: refactorer-agent, style-enforcer-agent, agent-tester-agent 3. **Infrastructure Tasks**: infrastructure-agent, cicd-agent 4. **Migration Tasks**: migration-assistant-agent, agent-tester-agent ### Phase 4: Quality Gates Between task groups, apply quality checks: - **Code Quality**: style-enforcer-agent, security-analyzer-agent, performance-analyzer-agent - **Test Coverage**: agent-tester-agent, test-writer-agent - **Documentation**: documentation-agent, review-plan ## Output Format Return structured results: - **Summary**: spec name, tasks completed/remaining, execution time - **Execution Plan**: phases, tasks, agents, execution type - **Results**: per-task status, agent used, duration, quality metrics - **Next Steps**: remaining tasks, blockers, recommendations ## Examples ``` "Implement the user-authentication spec" "Execute spec tasks for payment-integration" "Run the api-refactor spec with parallel execution" "Implement spec migration-plan --dry-run" ``` ## Delegation **Primary**: Invokes **agent-orchestrator-agent** (from development-codebase-tools plugin) with spec context, task dependencies, and execution configuration. **Fallback**: If agent-orchestrator-agent is unavailable, executes tasks sequentially using direct agent invocations based on task type.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.