Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Multi-Session Coding Project Blueprint Generator

agent planning skill risk: low

Multi-Session Coding Project Blueprint Generator

Converts a one-line objective into a step-by-step construction plan with self-contained context briefs for independent execution by fresh coding agents across multiple sessions or…

SKILL 1 file

SKILL.md
---
name: antigravity-awesome-skills-blueprint
description: "Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps."
---
# Blueprint — Construction Plan Generator

Turn a one-line objective into a step-by-step plan any coding agent can execute cold.

## Overview

Blueprint is for multi-session, multi-agent engineering projects where each step must be independently executable by a fresh agent that has never seen the conversation history. Install it once, invoke it with `/blueprint <project> <objective>`.

## When to Use This Skill

- Use when the task requires multiple PRs or sessions
- Use when multiple agents or team members need to share execution
- Use when you want adversarial review of the plan before execution
- Use when parallel step detection and dependency graphs matter

## How It Works

1. **Research** — Scans the codebase, reads project memory, runs pre-flight checks
2. **Design** — Breaks the objective into one-PR-sized steps, identifies parallelism, assigns model tiers
3. **Draft** — Generates the plan from a structured template with branch workflow rules, CI policy, and rollback strategies inline
4. **Review** — Delegates adversarial review to a strongest-model sub-agent (falls back to default model if unavailable)
5. **Register** — Saves the plan and updates project memory

## Examples

### Example 1: Database migration
```
/blueprint myapp "migrate database to PostgreSQL"
```

### Example 2: Plugin extraction
```
/blueprint antbot "extract providers into plugins"
```

## Best Practices

- ✅ Use for tasks requiring 3+ PRs or multiple sessions
- ✅ Let Blueprint auto-detect git/gh availability — it degrades gracefully
- ❌ Don't invoke for tasks completable in a single PR
- ❌ Don't invoke when the user says "just do it"

## Key Differentiators

- **Cold-start execution**: Every step has a self-contained context brief
- **Adversarial review gate**: Strongest-model review before execution
- **Zero runtime risk**: Pure markdown — no hooks, no scripts, no executable code
- **Plan mutation protocol**: Steps can be split, inserted, skipped with audit trail

## Installation

```bash
mkdir -p ~/.claude/skills
git clone https://github.com/antbotlab/blueprint.git ~/.claude/skills/blueprint
```

## Additional Resources

- [GitHub Repository](https://github.com/antbotlab/blueprint)
- [Examples: small plan](https://github.com/antbotlab/blueprint/blob/main/examples/small-plan.md)
- [Examples: large plan](https://github.com/antbotlab/blueprint/blob/main/examples/large-plan.md)

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

REQUIRED CONTEXT

  • project name
  • one-line objective

ROLES & RULES

  1. Use this skill only when the task clearly matches the scope described above.
  2. Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  3. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
  4. Don't invoke for tasks completable in a single PR.
  5. Don't invoke when the user says "just do it".

EXPECTED OUTPUT

Format
markdown
Constraints
  • each step must be independently executable by a fresh agent
  • include branch workflow rules, CI policy, and rollback strategies inline
  • pure markdown with no hooks or executable code

SUCCESS CRITERIA

  • Every step must be independently executable by a fresh agent
  • Each step must include a self-contained context brief

FAILURE MODES

  • May be invoked for single-PR tasks
  • May be invoked when user says "just do it"

EXAMPLES

Includes two examples of /blueprint command invocations (database migration and plugin extraction).

CAVEATS

Dependencies
  • codebase
  • project memory
Missing context
  • Explicit output template or schema for the step-by-step plan
  • Definition of success criteria for each generated step
Ambiguities
  • 'one-PR-sized steps' is undefined in terms of scope or size criteria
  • 'model tiers' and 'strongest-model sub-agent' are referenced but not defined
  • Exact output structure or template for the generated plan is not shown

QUALITY

OVERALL
0.78
CLARITY
0.85
SPECIFICITY
0.70
REUSABILITY
0.90
COMPLETENESS
0.65

IMPROVEMENT SUGGESTIONS

  • Add a concrete markdown template showing the required fields for each step (context brief, dependencies, rollback, etc.)
  • Define 'PR-sized' with examples of acceptable step granularity

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT