Plan phase-driven implementation with ADRs and task breakdowns.
npx skills add https://github.com/srednoff888-art/4 --skill plan-pipeline-start
Please help me install this Agent Skill. Skill: plan-pipeline-start Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/plan-pipeline/start Command: npx skills add https://github.com/srednoff888-art/4 --skill plan-pipeline-start
This planning skill helps teams produce a complete, governance-ready implementation plan before starting code, preventing scope creep and misaligned decisions.
Run the /plan-pipeline:start command to generate a complete implementation plan and relevant ADRs before coding.
High-intent search queries and answers about installing and using this skill.
The best way to create a governance-ready implementation plan is through a phase-driven workflow covering PRD analysis, design review, technical decisions, risk assessment, and metrics, which produces plan files, ADRs, and task breakdowns to prevent scope creep.
A phase-driven planning workflow is a structured process for large software initiatives that moves through PRD analysis, design review, technical decisions, dynamic research, and metrics to produce comprehensive implementation plans and architectural decision records.
You need to create ADRs and architecture decisions when planning large features requiring cross-team alignment, risk assessment, and governance metrics, ensuring technical choices are documented and approved before development begins.
To break down a PRD into task breakdowns and test plans, the planning process analyzes product requirements to generate structured artifacts including execution tasks, acceptance criteria, and governance metrics for the engineering team.
Yes, requirement analysis and governance planning work for cross-team coordination by applying a structured pipeline that aligns design reviews, architectural decisions, and risk assessments across participating teams before coding starts.
The limitations of a structured planning pipeline include the overhead required for comprehensive phase-driven documentation, making it less suitable for small features or rapid prototypes that do not require extensive PRD analysis, ADRs, or cross-team governance metrics.
BellaBeTransform Canvas strategy into structured product requirements and user stories.
juniorfonteneleCreate semantic branches, write code, run quality gates, and update progress tracking.
Cbanzaime23Generate structured test-design artifacts from PRD/ADR inputs.
StudentCristianFacilitate BDD requirements discovery using Example Mapping and Three Amigos sessions.
