pipeline-arch-review

Transform user stories into architecture decisions and ADR documentation.

3|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/I-Onlabs/claude-code-skills --skill pipeline-arch-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-arch-review
Source: https://github.com/I-Onlabs/claude-code-skills/tree/main/pipeline-arch-review
Command: npx skills add https://github.com/I-Onlabs/claude-code-skills --skill pipeline-arch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform PM specs into a structured architectural plan by producing Architecture Decision Records (ADRs) that capture decisions for system design.

Core Features & Use Cases

  • Design alternatives: generate 2-3 architectural approaches with tradeoffs.
  • ADR documentation: capture context, decisions, options, and rationale.
  • System design artifacts: define components, interfaces, data models, and error handling strategies; align with security and maintainability.
  • Use Case: When a feature requires architectural direction in design phase, produce ADR and component outline for implementation.

Quick Start

Provide the PM spec and let the Architecture Review stage output an ADR draft.

Frequently Asked Questions about pipeline-arch-review

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

FAQPage Schema
How do I turn product specs into architecture decision records?

To turn product specs into architecture decision records, provide the PM spec to generate an ADR draft that captures context, decisions, options, and rationale for system design.

What is ADR-driven architecture and when do I need it for system design?

ADR-driven architecture uses Architecture Decision Records to formally capture decisions, context, and rationale. It is needed during the Spec to Design phase when a feature requires clear architectural direction.

How do I generate design alternatives with tradeoffs for new features?

Generate design alternatives with tradeoffs by processing user stories to produce 2-3 architectural approaches, comparing their options and rationale within the resulting ADR documentation.

Can I define component interfaces and data models from user stories?

Yes, you can define component interfaces and data models from user stories. The architecture review outputs system design artifacts including interfaces, data models, and error handling strategies.

What is the best way to document security and testing considerations in system design?

The best way to document security and testing considerations is to align them within the ADR structure, capturing context and decisions alongside component designs, data models, and migration plans.

Does architecture review include a migration and rollback plan for new features?

Yes, architecture review includes a migration and rollback plan. It specifies research patterns, design alternatives, ADR structure, component interfaces, data models, security, testing, and rollback strategies.