plan

Automate software project plan reviews and generate ADR artifacts.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill plan-0xharbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/plan
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill plan-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to perform thorough, structured plan reviews that merge product thinking with engineering discipline, reducing misalignment and risk across initiatives.

Core Features & Use Cases

  • Phase-aligned evaluation: product rationale, architecture, security, tests, and production readiness in a single pass.
  • Mode-driven depth: EXPANSION, HOLD SCOPE, and REDUCTION to tailor the level of scrutiny.
  • Artifact generation: generates ADRs, decision logs, and a ready-to-handoff plan package.

Quick Start

Trigger a full plan review against the current project context to generate a structured assessment and ADR artifacts.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I automate architecture decision documentation and plan reviews for software projects?

Automate plan reviews by evaluating product rationale, architecture, security, and testing in a single pass to generate structured assessments, decision logs, and ADR artifacts for your software project.

What is an ADR artifact and when do I need traceable decision logs in software planning?

An ADR (Architecture Decision Record) artifact captures traceable design decisions made during plan reviews. You need them when merging product thinking with engineering discipline to reduce misalignment and risk across initiatives.

How do I conduct a phase-aligned plan review covering product, architecture, and production readiness?

Trigger a full plan review against your project context to evaluate product rationale, architecture, security, tests, and production readiness simultaneously, ensuring required frontmatter metadata and traceable decisions are generated.

Can I adjust the depth of scrutiny for software plan reviews based on project scope?

Yes, you can tailor scrutiny depth using EXPANSION, HOLD SCOPE, and REDUCTION modes to align the level of architectural and risk assessment with your current project exploration phase.

What is the best way to generate a ready-to-handoff plan package with risk assessment and design decisions?

Run a comprehensive plan review that merges product thinking with engineering discipline to produce a ready-to-handoff plan package containing generated ADRs, decision logs, and frontmatter metadata.