implementing

Orchestrate subagent-driven development tasks during the implementing phase.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/iclinic/afyapowers --skill implementing-iclinic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing
Source: https://github.com/iclinic/afyapowers/tree/main/src/skills/implementing
Command: npx skills add https://github.com/iclinic/afyapowers --skill implementing-iclinic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Implementing phase can be error-prone and slow when coordinating plan-driven tasks across subagents. This Skill orchestrates the flow, validates the phase, loads plan and design context, and triggers the subagent-driven development to execute tasks reliably.

Core Features & Use Cases

  • Orchestrates plan execution by delegating tasks to the subagent-driven development flow.
  • Validates the current feature is in the implement phase and reads artifacts from the repository to guide execution.
  • Updates state, surfaces implementation concerns, and hands off to the next phase when complete.
  • Use Case: When a feature plan is ready for implementation, run this skill to orchestrate execution with subagents and reconcile results.

Quick Start

Start the implementing phase for the active feature and delegate tasks to the subagent-driven development flow.

Frequently Asked Questions about implementing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate subagent tasks for feature implementation?

Orchestrating subagent tasks for feature implementation involves validating the active feature is in the implement phase, loading plan and design context, and dispatching required sub-skills to execute development tasks reliably.

What is the best way to coordinate plan-driven tasks across multiple subagents?

Coordinating plan-driven tasks across subagents requires a workflow orchestration skill that validates the current phase, reads repository artifacts, and triggers subagent-driven development to execute tasks.

Can I use workflow orchestration to manage phase transitions during development?

Yes, workflow orchestration can manage phase transitions by updating state artifacts and handing off to the next phase after subagent-driven development tasks complete and surface any implementation concerns.

How do I validate that a feature is ready for the implementing phase?

Validating a feature for the implementing phase means checking that the feature plan is ready and reading repository artifacts to confirm the active feature state matches the required implement phase.

What are the limitations of subagent-driven development for task execution?

Subagent-driven development depends on accurate plan and design context loaded from repository artifacts; if the feature state is invalid or context is missing, the orchestration flow cannot reliably execute tasks.

Why does implementing phase orchestration need to load plan and design context?

Implementing phase orchestration loads plan and design context to guide subagent-driven development, ensuring that dispatched sub-skills execute tasks based on validated repository artifacts and feature specifications.