blueprint

Create dependent step-by-step plans for multi-session, multi-agent development workflows.

3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/rlagycks/oh-my-forge --skill blueprint-rlagycks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/rlagycks/oh-my-forge/tree/main/skills/blueprint
Command: npx skills add https://github.com/rlagycks/oh-my-forge --skill blueprint-rlagycks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill converts high-level objectives into detailed, step-by-step construction plans suitable for execution across multiple sessions and agents.

Core Features & Use Cases

  • Automated Planning: Breaks down complex tasks into manageable steps with dependency mapping.
  • Multi-agent Coordination: Facilitates parallel execution and cross-session continuity.
  • Use Case: Planning a large software refactor that requires multiple development cycles and team coordination.

Quick Start

Give the /blueprint command with your project name and a clear task description to generate a comprehensive, ready-to-execute plan.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I create a multi-step development plan for a complex software refactor?

To create a multi-step development plan, define your high-level objective and use the planning command to automatically break it down into manageable, dependent steps. This maps dependencies and structures execution across multiple sessions.

What is a dependency graph in multi-agent development workflows?

A dependency graph in multi-agent workflows maps out task relationships, enabling parallel execution and cross-session continuity. It allows multiple agents to execute independent steps simultaneously while maintaining structured execution order.

Can I plan tasks across multiple project branches and repositories?

Yes, you can plan tasks across multiple project branches and repositories. The planning process supports cross-repository coordination, allowing you to map dependencies and manage multi-session development workflows seamlessly.

Does the project management planning process require external code execution?

The project management planning process does not require external code execution. It operates entirely within Markdown, ensuring full process transparency and safety by generating structured plans without executing external scripts.

What is the best way to automate planning for multi-agent coordination?

The best way to automate planning for multi-agent coordination is providing a clear task description to generate a comprehensive plan. This creates a dependency graph that facilitates parallel execution and enables adversarial review.

When should I not use automated planning for development workflows?

You should not use automated planning for development workflows if your task requires immediate code execution or lacks a clear, high-level objective. The process focuses on generating Markdown plans rather than executing code directly.