plan-pipeline

Coordinate product planning into ADR-backed implementation plans with five pipeline stages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill plan-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-pipeline
Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/plan-pipeline
Command: npx skills add https://github.com/srednoff888-art/4 --skill plan-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Pipeline orchestrates the full planning lifecycle from initial request to validated plan, ADRs, and handoff to execution, ensuring governance and traceability before any code is written.

Core Features & Use Cases

  • End-to-end orchestration: coordinates five stages—ceo-review, eng-review, start, validate, and execute—into a single workflow.
  • Flexible execution: run the full pipeline or start from any stage to fit complex projects.
  • Artifact generation: produces structured plans, ADRs, and decision records in docs/plans for auditability.

Quick Start

Run /plan-pipeline to execute the full planning pipeline from start to finish.

Frequently Asked Questions about plan-pipeline

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

FAQPage Schema
How do I create ADR-backed implementation plans from initial product requests?

To create ADR-backed implementation plans, you orchestrate a product request through a multi-stage review pipeline that enforces governance, validates architecture decisions, and outputs structured artifacts to your docs/plans directory.

What is the best way to manage end-to-end product planning and architecture governance?

End-to-end product planning and architecture governance is managed by translating requests into validated plans using a coordinated workflow that tracks decisions, risks, and design artifacts across distinct review phases.

Can I start a planning workflow from a specific phase instead of running the full pipeline?

Yes, you can start the planning workflow from any specific phase. The pipeline supports flexible execution, allowing you to begin at stages like eng-review or validate to fit complex project workflows without rerunning earlier steps.

Do I need any external dependencies to orchestrate architecture decision records?

No external dependencies are required to orchestrate architecture decision records. The pipeline operates independently to generate design artifacts and track governance decisions within your local docs/plans directory.

How does the pipeline handle plan changes and track risks during execution?

The pipeline handles plan changes and tracks risks by enforcing governance throughout its phases, ensuring every architectural modification and risk assessment is documented as a structured decision record in the docs/plans directory.

When should I not use a full pipeline approach for workflow planning?

You should not use a full pipeline approach for workflow planning when a project only requires isolated stage execution, as the system is designed to support starting from any phase rather than forcing a complete end-to-end run.