dev-agent

Orchestrate chunk-based feature development with progress reporting and blocker escalation.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/clouseryan/agentic-skills --skill dev-agent-clouseryan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-agent
Source: https://github.com/clouseryan/agentic-skills/tree/main/dev-team/developer
Command: npx skills add https://github.com/clouseryan/agentic-skills --skill dev-agent-clouseryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines complex feature development by chunking work and enforcing architectural patterns.

Core Features & Use Cases

  • Chunk-based task orchestration: breaks large features into auditable chunks and assigns them to the appropriate agent roles.
  • Pattern compliance and blocker escalation: ensures work follows existing codebase conventions and flags blockers immediately.
  • Progress reporting and rework handling: provides status updates after each chunk and follows the rework protocol when feedback is received.

Quick Start

Provide a chunk specification to initiate a chunk-driven feature implementation and let the dev-agent execute one chunk at a time.

Frequently Asked Questions about dev-agent

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

FAQPage Schema
How do I break down complex feature development into manageable codebase chunks?

Complex feature development is streamlined by breaking work into auditable chunks, enforcing architectural patterns, and assigning each chunk to appropriate agent roles for deterministic execution.

How does pattern compliance work when implementing multiple coordinated code chunks?

Pattern compliance ensures every implemented chunk follows existing codebase conventions, immediately flagging architectural deviations as blockers for escalation rather than continuing with non-conforming code.

What is the best way to handle rework feedback during chunk-based code implementation?

Rework feedback during chunk-based code implementation is handled by following a structured rework protocol, providing status updates after each chunk, and applying feedback deterministically before proceeding.

Do I need to provide a chunk specification to start a chunk-driven feature implementation?

Yes, you need to provide a chunk specification to initiate chunk-driven feature implementation, which allows the engine to execute one chunk at a time while enforcing architectural patterns.

How does progress reporting work for end-to-end tasks requiring multiple coordinated chunks?

Progress reporting for end-to-end tasks provides status updates after each coordinated chunk is executed, ensuring visibility into the deterministic chunk execution and immediate visibility of any blockers.

When should I use a chunk-driven code implementation engine instead of standard development workflows?

Use a chunk-driven code implementation engine for end-to-end tasks requiring multiple coordinated chunks, strict architectural pattern conformity, auditable progress reporting, and structured blocker escalation.