building

Coordinate subagents to execute plans with post-task review and architecture checks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill building-djwmobley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building
Source: https://github.com/djwmobley/pipeline/tree/main/skills/building
Command: npx skills add https://github.com/djwmobley/pipeline --skill building-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagent-driven plan execution enables a plan to be implemented by dispatching a fresh subagent for each task and conducting a post-task review to ensure quality and alignment with the architecture plan.

Core Features & Use Cases

  • Fresh subagent per task to isolate responsibilities and accelerate iteration.
  • Post-task review to catch issues early and enforce standards.
  • Build-state and architecture-checks for consistency across tasks.

Quick Start

Dispatch a plan to run with subagents and enable post-task review after each task.

Frequently Asked Questions about building

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

FAQPage Schema
How do I coordinate subagents for autonomous plan execution?

Subagent-driven plan execution coordinates autonomous subagents by dispatching a fresh subagent for each independent task, isolating responsibilities to accelerate iteration and enforce a strict reporting contract.

What is post-task review in architecture compliance?

Post-task review is a validation mechanism that checks architecture compliance and catches issues early after each subagent completes its task, ensuring ongoing alignment with the overall architecture plan.

How do context stores ensure deterministic results in subagent orchestration?

Context stores ensure deterministic results by maintaining consistent build-state and architecture-checks across tasks, providing subagents with isolated context for iterative validation throughout the orchestration process.

Can I use subagent orchestration for mostly independent tasks?

Yes, subagent orchestration specifically targets tasks that are mostly independent and require iterative validation after each task, dispatching a fresh subagent per task to isolate responsibilities effectively.

Does subagent-driven plan execution require a strict reporting contract?

Yes, the orchestrator enforces a strict reporting contract to ensure quality and alignment with the architecture plan, conducting post-task reviews to catch issues early across all coordinated subagent executions.

What are the limitations of dispatching a fresh subagent per task?

Dispatching a fresh subagent per task is limited to mostly independent tasks requiring iterative validation; highly interdependent tasks may not benefit from the isolated context stores and strict reporting contract approach.