blueprint

Break broad engineering objectives into executable multi-step implementation plans.

Updated Jun 24, 2026

Search Tags:#planning #verification #migration #multi-agent #roadmap #refactor #dependency graph

Ready to run

npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill blueprint-mostafa-ismail-2004

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/blueprint
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill blueprint-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a broad, one-line objective into a concrete construction plan for large engineering work that spans multiple sessions, multiple agents, or multiple pull requests.

Core Features & Use Cases

Stepwise planning: Breaks complex goals into ordered, one-PR-sized steps with clear dependency links.
Cold-start handoff: Gives each step a self-contained context brief so a fresh agent can continue without reading the whole history.
Review and safety: Includes adversarial review, anti-pattern checks, rollback considerations, and plan mutation rules.
Use case: Use it when you need a roadmap for a migration, refactor, platform change, or any multi-session engineering project.

Quick Start

Ask for a blueprint for your project goal and let the skill produce a step-by-step execution plan with dependencies, validation, and review gates.

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 engineering refactor into a multi-step implementation plan?▼

To break a large engineering refactor into a multi-step implementation plan, you need stepwise planning that divides the objective into ordered, one-PR-sized steps with clear dependency links. This produces self-contained steps with verification and rollback guidance.

What is the best way to plan a multi-PR migration for a fresh development agent?▼

The best way to plan a multi-PR migration for a fresh agent is to use cold-start handoff context briefs. This gives each step a self-contained context brief so a fresh agent can continue working without reading the whole history.

How do you create a dependency graph for parallel sub-agent workstreams?▼

Creating a dependency graph for parallel sub-agent workstreams involves breaking a broad objective into ordered steps with clear dependency links. This approach ensures each step is properly sequenced before parallel execution begins.

Does multi-session engineering planning include rollback guidance and review checks?▼

Yes, multi-session engineering planning includes rollback guidance and review checks. The plan incorporates adversarial review, anti-pattern checks, and rollback considerations to ensure safety during complex platform changes and migrations.

When do I need a roadmap for a multi-session platform change?▼

You need a roadmap for a multi-session platform change when a broad engineering objective spans multiple sessions, agents, or pull requests. It converts one-line objectives into concrete construction plans with validation and review gates.