feat: register Blueprint in community catalog

[chordpli]

Extension Submission

Extension Name: Blueprint
Extension ID: blueprint
Version: 1.0.0
Author: chordpli
Repository: https://github.com/chordpli/spec-kit-blueprint

Description

Pre-implementation blueprint generator. Reads spec artifacts (tasks.md, spec.md, plan.md) and produces a single blueprint.md with complete, ready-to-use content for every task — so developers can review, understand, and type through the implementation before /speckit.implement runs.

By typing through the blueprint, the developer:

• Reads the implementation before it exists — understands what files will be created and how they connect
• Learns the project's conventions by following real, working examples
• Catches design issues and incorrect assumptions before any code is committed

Blueprint is entirely optional — /speckit.implement works with or without it.

Commands: /speckit.blueprint.generate [doc-only|scaffold], /speckit.blueprint.validate
Hook: after_tasks (optional prompt to generate blueprint after task generation)

Checklist

• Valid extension.yml manifest
• README.md with installation and usage docs
• LICENSE file included (MIT)
• CHANGELOG.md included
• GitHub release created (v1.0.0)
• Download URL accessible (archive/refs/tags/v1.0.0.zip → HTTP 200)
• Repository is public
• Extension tested on real project
• All commands working
• No security vulnerabilities
• Added to extensions/catalog.community.json (alphabetical order)
• Added to Community Extensions table in README.md (alphabetical order)

Testing

• macOS (Darwin 23.5.0, arm64) with spec-kit 0.7.2
• Tested with local dev install: specify extension add --dev /path/to/spec-kit-blueprint
• Generated blueprint for a real project (Kotlin + Next.js, 100 tasks, 10 phases)
• Validated: manifest parsing, command registration, hook registration, scaffold validation script
• uv run pytest tests/test_extensions.py — 165 passed

AI Disclosure

• I did use AI assistance (describe below)

The idea, initial design, and core structure were authored by me. AI was used to refine the extension across multiple review rounds:

• Senior backend/frontend/tech-lead reviews to catch code quality issues in generated blueprints
• Prompt engineer reviews to make the command instructions technology-agnostic (removing framework-specific terms)
• Server engineer review to add security guardrails (zero-secrets rule, environment config completeness)
• Iterative testing on a real project to validate and improve blueprint output quality

[Copilot]

Pull request overview

Adds the Blueprint extension to the Spec Kit community extension catalog so it can be discovered and installed by users.

Changes:

• Added a blueprint entry to extensions/catalog.community.json with metadata (URLs, version, tags, capabilities).
• Added a corresponding row to the Community Extensions table in the root README.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
extensions/catalog.community.json	Registers the Blueprint extension in the community catalog.
README.md	Lists Blueprint in the Community Extensions table for discoverability.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chordpli]

Why this extension

Spec Kit's workflow goes from /speckit.tasks straight to /speckit.implement. There is no built-in step to preview what files will be created or modified before AI writes them.

Blueprint inserts an optional pre-flight review step. It generates blueprint.md — a complete, task-by-task document showing every file, every change, and every decision, organized by dependency order and phase.

What it's for:

• Pre-flight review — see the full scope of changes (new files, modifications, deletions) before any code is committed. Catch wrong designs or missing edge cases at the blueprint stage, not in a 50-file PR diff
• Scaffold mode — optionally creates the file structure on disk with structural files complete and core logic as TODO stubs. Lets you verify the project structure before implementation fills it in
• Codebase familiarity — the blueprint reads existing project files and follows the same patterns, so reviewing it keeps you connected to the conventions and architecture as the project grows

How it differs from architect-preview / critique:

Those extensions analyze risk and strategy at the spec/plan level. Blueprint operates at the file level — it shows the actual code and configuration changes that will be made, task by task.

What it's not:

• Not a required step — /speckit.implement works with or without it
• Not a token optimization tool — it adds a generation step, not replaces one
• Not auto-executed — the only hook (after_tasks) is optional and user-prompted

When to use it:

Recommended for features with 10+ tasks where the implementation spans multiple modules or phases. For small 2-3 task changes, running /speckit.implement directly is simpler.

Two commands: generate (doc-only or scaffold) and validate (checks scaffold correctness).

Tested on a real project with 100 tasks across 10 phases.

[Copilot]

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 2

[mnriem]

Please address Copilot feedback

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chordpli]

@mnriem Thank you for the detailed comments. I've incorporated all the feedback provided by Copilot into the latest commit.

[mnriem]

Thank you!