plan-implement

Orchestrate an agent team to implement tasks from PLANS.md with progress tracking and verification.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/lucaswall/food-scanner --skill plan-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-implement
Source: https://github.com/lucaswall/food-scanner/tree/main/.claude/skills/plan-implement
Command: npx skills add https://github.com/lucaswall/food-scanner --skill plan-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates parallel plan execution by orchestrating an agent team to implement tasks from PLANS.md, ensuring non-overlapping ownership and real-time verification.

Core Features & Use Cases

  • Team-based plan execution: Breaks down PLANS.md into work units, spawns workers, and prevents file conflicts.
  • Real-time coordination: Updates Linear issues and coordinates verification, handling generated artifacts when needed.
  • Fallback to single-agent mode: Automatically switches to a single-agent approach if agent teams are unavailable.

Quick Start

Kick off parallel plan execution by creating a team and partitioning PLANS.md into work units. If team creation fails, fall back to a single-agent flow.

Frequently Asked Questions about plan-implement

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

FAQPage Schema
How do I coordinate parallel task execution from a plan file without file conflicts?

Coordinate parallel task execution by orchestrating an agent team to implement tasks from PLANS.md, ensuring non-overlapping file ownership and real-time verification. It partitions work units and spawns workers to prevent file conflicts.

Can I update Linear issues automatically while running parallel plan implementation?

Yes, parallel plan implementation updates Linear issues in real-time during task execution. The agent team coordinates progress tracking and verification, automatically syncing issue statuses as workers complete their assigned work units.

What happens if agent teams are unavailable when partitioning work from PLANS.md?

If agent teams are unavailable, the system automatically falls back to a single-agent mode for plan implementation. This ensures tasks from PLANS.md still execute sequentially without requiring team orchestration capabilities.

How does task partitioning handle generated artifacts and CLI tasks during team orchestration?

Task partitioning handles generated artifacts and CLI tasks by assigning lead responsibilities during team orchestration. The agent team coordinates verification and manages these artifacts when generated during parallel plan execution.

Does this parallel workflow automation approach work for projects with strict file-ownership constraints?

Yes, this workflow automation approach is designed for projects with strict file-ownership constraints. It coordinates parallel plan execution by assigning non-overlapping file ownership to spawned workers, preventing conflicts.

What is the best way to break down a large project plan into parallel work units for an agent team?

The best way to break down a large project plan is partitioning PLANS.md into discrete work units and spawning workers with non-overlapping file ownership. This team-based plan execution enables real-time coordination and verification.