Skip to main content
Project ZIP packages the approved current Blueprint for implementation. It remains locked until all 10 current document cards, including any Not Required stub, are Reviewed and you complete Sign Approve Blueprint.

​
What the ZIP contains

  • the PRD Markdown file and connected Blueprint documents under docs/;
  • README.md with project-specific setup and workflow instructions;
  • .env.example and .env.local.example with stack-aware parameter names and safe placeholders;
  • canonical coding-agent rules in AGENTS.md, plus AGENT.md as a compatibility pointer;
  • five ordered prompts under ai-coding-agent-prompts/;
  • optional working-document templates under templates/;
  • a manifest that lists the package contents, prompt order, environment parameters, and implementation-kit paths.
Environment templates contain no real credentials. Add secrets only to ignored local files or your deployment secret manager. Never paste secrets into a coding-agent prompt, commit, log, or screenshot.

​
Merge the package safely

1

Extract into a separate folder

Inspect the package before copying files into a repository.
2

Preserve existing project rules

In a new repository, place AGENTS.md and AGENT.md at the root. In an existing repository, ask the coding agent to merge relevant bundle rules into the existing AGENTS.md. Do not overwrite human instructions, source code, configuration, or local changes.
3

Copy the product inputs

Add the PRD, docs/, ai-coding-agent-prompts/, templates/, and the environment examples. Reconcile an existing README.md instead of replacing it.
4

Prepare local configuration

Reconcile .env.example. Create .env.local from .env.local.example only when local development needs it, preserve existing values, add missing names, and keep the file ignored by Git.
5

Check Git

Use the repository’s current remote when one exists. Provide a Git URL only when the repository has no remote; never replace an existing remote without explicit approval.
AGENTS.md is the single canonical agent contract. AGENT.md intentionally contains only a pointer, so two copies of the rules cannot drift.

​
Run the five prompts in order

Do not run Step 4 merely to make work appear faster. Keep one coordinator, explicit ownership, and an integration order whenever multi-agent mode is active.

​
Working-document templates

The templates/ directory provides starting structures for:
  • PLAN.md, the only active implementation plan;
  • STATUS.md, the latest concise project snapshot;
  • LOG.md, an append-only work history;
  • CONSOLIDATION_AGENT.md, used only during real multi-agent execution;
  • minimum Git-ignore patterns for local environment files.
Step 1 creates or reconciles active root documents from these templates. It must preserve useful existing content. A legacy IMPLEMENTATION_PLAN.md is migration input, not a second active plan.

​
Before the first coding run

  1. Read the packaged README.md and PRD.
  2. Confirm that AGENTS.md preserves the repository’s human rules.
  3. Fill required local configuration without committing secrets.
  4. Confirm the Git remote, or provide a repository URL only if no remote exists.
  5. Give the coding agent the Step 1 prompt first, then review PLAN.md before Step 2.
If global Blueprint approval is invalidated by regeneration, restore, or a new version, review and approve the current set again before downloading a replacement ZIP.