blueprint

Generates multi-PR construction plans with adversarial review and self-contained step briefs.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill blueprint-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/NalinDalal/skillset/tree/main/skills/architecture/blueprint
Command: npx skills add https://github.com/NalinDalal/skillset --skill blueprint-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex features are hard to break into reviewable, executable chunks. This Skill turns a one-line objective into a structured multi-PR plan where each step is self-contained enough for any agent to execute cold, with review gates to catch planning errors before code is written. ## Core Features & Use Cases - Step Brief Generation: Each step gets a brief with objective, files to create/modify, dependencies, implementation details, verification checklist, and rollback plan. - Adversarial Review: A stronger model reviews the plan against a checklist covering step ordering, dependencies, scope, and hidden complexity, returning a verdict like NEEDS REVISION. - Plan Mutation Protocol: Supports splitting, inserting, skipping, and reordering steps with an audit trail as requirements change. - Use Case: You need to add JWT authentication to a monorepo. The Skill produces Step 1 (user schema), Step 2 (user model), Step 3 (JWT auth), each mapped to its own branch and PR with verification criteria. ## Quick Start Ask the agent to create a blueprint that breaks your feature objective into ordered PR-sized steps with verification and rollback plans.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I break a large feature into multiple pull requests?▼

Define the objective in one line, research the codebase, then split work into steps where each step equals one PR. Each step gets a brief with files, dependencies, implementation details, verification, and a rollback plan.

What is adversarial review in implementation planning?▼

Adversarial review means having a stronger model critique the plan before execution. It checks step ordering, dependency clarity, scope size, and hidden complexity, then returns issues, recommendations, and a verdict such as NEEDS REVISION.

How do I handle plan changes during multi-step implementation?▼

Use the plan mutation protocol: split oversized steps (4a/4b), insert newly discovered work (Step 3.5), skip deprioritized steps, or reorder steps when dependencies change. Every mutation records an audit trail entry.

What naming convention should PRs follow in a step-based plan?▼

Name each PR as 'Step N: Brief description', for example 'Step 3: JWT Authentication' or 'Step 4a: User Registration'. Create a matching feature branch per step and open the PR against main.

When should I not use a multi-PR blueprint approach?▼

Avoid it for small, single-commit changes where planning overhead exceeds the work itself. It is designed for complex features spanning multiple files, packages, or dependencies that benefit from review gates and rollback plans.