develop

Execute approved implementation plans with parallel developer tasks and full verification.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill develop-alexiolan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/develop
Command: npx skills add https://github.com/alexiolan/craft-skills --skill develop-alexiolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Develop orchestrates execution of an approved implementation plan by initializing shared state, dispatching parallel developer agents, and performing integration review along with full verification (lint, tsc, format, and build).

Core Features & Use Cases

  • Initialize shared state for coordinated runs
  • Dispatch parallel developer agents to implement plan tasks
  • Perform integration review and end-to-end verification (lint, type-check, format, build)
  • Auto-detect plans when possible and auto-detect latest plan

Quick Start

Provide an approved implementation plan path and let Develop execute the plan while verifying and reporting results.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I execute an implementation plan with parallel developer agents?

To execute an implementation plan with parallel developer agents, provide the approved plan path. The Skill initializes shared state, dispatches parallel tasks, and performs integration review with full verification including lint, type-check, format, and build.

What is the best way to coordinate shared state across parallel developers during plan execution?

Coordinating shared state across parallel developers requires initializing a `.shared-state.md` file before dispatching tasks. This ensures synchronized plan execution and outputs updated shared state alongside a log of actions taken.

How does plan execution verification handle linting, type checking, and building?

Plan execution verification handles linting, type checking, and building as a final-step gate. After dispatching parallel developer agents, it runs integration review and performs full verification using lint, tsc, format, and build checks.

Can I auto-detect an implementation plan path instead of providing it manually?

Yes, you can auto-detect an implementation plan path. The Skill targets projects where a plan exists or can be auto-detected, automatically identifying the latest approved plan to initialize shared state and dispatch parallel developer tasks.

Do I need specific project conventions to orchestrate parallel tasks for plan execution?

Orchestrating parallel tasks for plan execution requires `.shared-state.md`, `.claude/reuse-index.md`, and `AGENTS.md` conventions. These files establish the shared state and project guidelines needed to dispatch and integrate parallel developer agents.

Why does parallel plan execution require integration review after dispatching developer tasks?

Parallel plan execution requires integration review after dispatching developer tasks to consolidate parallel work into a cohesive state. It performs end-to-end verification, running lint, tsc, format, and build as a last-step gate to ensure code quality.