implement-task

Name: implement-task
Availability: InStock
Author: corbinatorx

Execute development tasks from phase files with strict scope adherence.

Updated Dec 25, 2025

Search Tags:#developer workflow #code generation #task implementation #blueprint adherence #phase files #builder agent

Ready to run

npx skills add https://github.com/CorbinatorX/devops-ai-toolkit-claude-plugin --skill implement-task-corbinatorx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-task
Source: https://github.com/CorbinatorX/devops-ai-toolkit-claude-plugin/tree/main/skills/implement-task
Command: npx skills add https://github.com/CorbinatorX/devops-ai-toolkit-claude-plugin --skill implement-task-corbinatorx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the precise implementation of development tasks defined in phase files, ensuring adherence to architectural blueprints and project conventions.

Core Features & Use Cases

Task Execution: Implements specific, granular tasks outlined in phase files.
Scope Discipline: Strictly adheres to specified file locations and task requirements.
Blueprint Alignment: Follows architectural patterns defined in blueprints.
Use Case: A developer receives a task to implement a new API endpoint. They use this Skill, providing the task reference, and the Skill's builder agent creates the controller, service logic, and adds necessary error handling as specified, updating task completion status.

Quick Start

Implement the task specified as payment-service/phase1#2.1.

Frequently Asked Questions about implement-task

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

FAQPage Schema

How do I automate code generation for specific tasks from phase files?▼

Executing development tasks from phase files requires parsing task references to locate exact file paths for code modification. The builder agent processes these references to implement granular requirements while maintaining strict scope discipline and adhering to architectural blueprints.

What is the best way to maintain scope discipline when implementing architectural blueprints?▼

Maintaining scope discipline during blueprint implementation involves strictly adhering to specified file locations and task requirements defined in phase files. This prevents unauthorized modifications outside the defined architectural boundaries and ensures granular task execution aligns with project conventions.

How do I implement a new API endpoint using a builder agent and phase files?▼

Implementing an API endpoint requires providing the builder agent with a task reference like payment-service/phase1#2.1. The agent then creates the controller, service logic, and error handling as specified in the phase file, updating task completion status upon successful implementation.

Does task implementation require manual checkbox updates after generating code?▼

Task implementation does not require manual checkbox updates. The builder agent automatically manages task completion status by updating checkboxes in the phase files after successfully creating or modifying code at the specified file locations.

What format do task references need to be in for phase file execution?▼

Task references for phase file execution follow a structured format combining the service name, phase identifier, and task number, such as payment-service/phase1#2.1. Parsing this reference allows the builder agent to locate the exact phase file and implement the corresponding task.

When should I not use a builder agent for phase file task implementation?▼

You should not use a builder agent for phase file task implementation when modifications are needed outside the specified file locations or when deviating from the established architectural blueprints. This approach enforces strict scope discipline and cannot handle tasks lacking defined phase file references.