plan-architect

Translate specifications into PLAN.md, ARCHITECTURE.md, and per-FASE implementation artifacts.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill plan-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-architect
Source: https://github.com/noelserdna/claude-plugin-sdd/tree/main/skills/plan-architect
Command: npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill plan-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan-Architect translates complete specifications into actionable implementation artifacts, enabling a clean, traceable bridge from requirements to concrete execution plans across multiple phases.

Core Features & Use Cases

  • Interactive phase planning that maps specifications to FASEs with dependencies and deliverables.
  • Architecture-aware planning that produces ARCHITECTURE.md and per-phase artifacts aligned with reference frameworks.
  • Decision traceability through ADRs, CLARIFICATIONS.md, and RESEARCH.md to preserve rationale.
  • Per-FASE planning that generates PLAN-FASE-{N}.md with detailed decisions, APIs, data changes, tests, and acceptance criteria.
  • Incremental, audit-friendly outputs: PLAN.md, CLARIFY-LOG.md, and RESEARCH.md without modifying source specs.

Quick Start

Run plan-architect on your spec repository to generate the full planning artifacts. Use the per-FASE option to focus on a single phase, or audit the plan with the built-in checks. Review the resulting PLAN.md and ARCHITECTURE.md to align implementation with the spec.

Frequently Asked Questions about plan-architect

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

FAQPage Schema
How do I translate software specifications into actionable implementation plans?

Translating software specifications into actionable implementation plans involves orchestrating Clarify, Architecture, and Plan phases to generate PLAN.md and ARCHITECTURE.md files, ensuring a clean, traceable bridge from requirements to concrete execution without modifying source specs.

How do I maintain architecture decision traceability across multiple implementation phases?

Maintaining architecture decision traceability requires consulting ADRs, CLARIFICATIONS.md, and RESEARCH.md during phase planning. This preserves rationale across FASEs by logging decisions and mapping dependencies into per-phase artifacts like PLAN-FASE-{N}.md.

What is the best way to map specifications to per-phase deliverables and dependencies?

Mapping specifications to per-phase deliverables requires interactive phase planning that generates PLAN-FASE-{N}.md files. Each artifact details specific decisions, APIs, data changes, tests, and acceptance criteria aligned with the reference architecture.

Can I generate an architecture design without altering my original spec files?

Generating an architecture design without altering original specs is fully supported. The process produces audit-friendly outputs like ARCHITECTURE.md, CLARIFY-LOG.md, and RESEARCH.md incrementally, ensuring your source specification repository remains completely unmodified.

Does plan-architect require any specific dependencies to run on a spec repository?

Running plan-architect on a spec repository requires no external dependencies. It operates directly on your complete specifications to orchestrate the Clarify, Architecture, and Plan phases, outputting all necessary planning artifacts independently.

What limitations exist when auditing incremental outputs like CLARIFY-LOG.md?

Limitations when auditing incremental outputs like CLARIFY-LOG.md center on its scope as a decision log rather than an active spec modifier. It records clarifications and research rationale for traceability but cannot execute or enforce those decisions automatically.