blueprint

Decompose software objectives into dependency-aware pull request plans.

Updated Jan 6, 2023
One-click install
npx skills add https://github.com/pekral/phpstan-rules --skill blueprint-pekral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/pekral/phpstan-rules/tree/main/.claude/skills/blueprint
Command: npx skills add https://github.com/pekral/phpstan-rules --skill blueprint-pekral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of managing large, multi-session engineering objectives that are too broad for a single pull request, preventing scope creep and ensuring consistent progress.

Core Features & Use Cases

  • Sequenced Planning: Breaks down complex tasks into 3-12 manageable, independently reviewable pull requests.
  • Dependency Mapping: Establishes clear dependency edges between steps to identify what can be done in parallel versus what must be sequential.
  • Cold-Start Readiness: Generates self-contained context briefs for every step, allowing different agents or developers to pick up work without prior knowledge.

Quick Start

Use the blueprint skill to create a multi-step construction plan for the proposed database migration project.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I break down a complex software engineering objective into multiple pull requests?

To break down a complex software engineering objective into multiple pull requests, you decompose the overarching task into a sequenced plan of 3-12 individual, independently reviewable PRs. This prevents scope creep and ensures consistent progress across multi-session development workflows.

What is dependency mapping for parallel software development workflows?

Dependency mapping for parallel software development workflows establishes clear dependency edges between planned pull requests. This process identifies which engineering steps can be executed in parallel and which must be sequential to maintain architectural integrity.

Can I use a multi-step planning approach for large refactoring projects across different sessions?

Yes, you can use multi-step planning for large refactoring projects across different sessions. The approach generates self-contained context briefs for every step, allowing different agents or developers to pick up work cold without prior knowledge of the architecture.

What is the best way to ensure each step of a database migration project is independently mergeable?

The best way to ensure each step of a database migration project is independently mergeable is to sequence the work into dependency-aware pull requests. This requires strict adherence to specific git, architecture, and documentation conventions to maintain traceability.

When should I not use a sequenced pull request plan for engineering tasks?

You should not use a sequenced pull request plan for engineering tasks that are small enough to fit into a single reviewable code contribution. This planning method is specifically designed for broad, multi-session objectives that require 3 to 12 distinct PRs to prevent scope creep.