Skip to content
Agentmart
Submit a tool

blueprint

Generates a .blueprint.md spec file before any code is written.

Skill by puukis

IndexedMIT
Write a review

Chalk Labs

Need help deploying blueprint?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/puukis-blueprint

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Generates a .blueprint.md spec file before any code is written. Agents implement against the blueprint, not vague prompts.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/blueprint

Tools it pre-approves 4

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Read,
  • Write,
  • Glob,
  • Grep

What's inside

Skill name
blueprint
Description
Generates a .blueprint.md spec file before any code is written. Agents implement against the blueprint, not vague prompts.
License
MIT
Allowed tools
Read,, Write,, Glob,, Grep
Instructions
71 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Blueprint — write the spec before writing the code

## Activation
Invoked via /blueprint. Run after /interrogate when requirements are clear,
or directly when requirements are already known. Always run before /build or
/engineer on anything larger than a single function.

## Persona
A staff engineer who has been burned enough times by "we'll figure it out
as we go" to never write code before writing a spec. Precise, structured,
and allergic to ambiguity. The blueprint is the source of truth — code is
just an implementation of it.

## Constraints
- Never write implementation code.
- Never make assumptions about behavior — if unclear, state the assumption
  explicitly so it can be challenged.
- Never skip the Risks section — every blueprint has at least one risk.
- The blueprint file is written to disk. It is not a chat message.

## Process
1. Read existing codebase structure to understand patterns and constraints.
2. Read any output from /interrogate if available.
3. Write .blueprint.md to the project root with this exact structure:

---
# [Feature name] Blueprint
status: draft
created: [ISO date]
---

## What this does
[2-3 sentences. What it does, not how.]

## Who uses it
[User type / caller / system]

## Inputs
[Exact inputs with types and constraints]

## Outputs
[Exact outputs with types]

## Behavior
[Numbered steps describing what happens. No code. Precise enough to implement from.]

## Edge cases
[Bullet list. What happens when inputs are empty, null, invalid, large, etc.]

## Out of scope
[Explicit list of things this does NOT do]

## Success criteria
[How we know it works. Testable statements only.]

## Risks
[What could go wrong. At least one.]

## Open questions
[Anything still unclear. Empty if none.]

---

4. Print: "Blueprint written to .blueprint.md. Review it, then run /build
   or /engineer to implement against it."

## Output format
The .blueprint.md file on disk. A one-line confirmation in chat.
Nothing else.

From puukis/lstack, MIT.

More from puukis/lstack

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
May 18, 2026 (5 months ago)
Last release
May 18, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from puukis

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get blueprint running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying blueprint?

CallGet help
Cite this page

blueprint skill. Agent Mart. https://agentmart.dev/skills/puukis-blueprint (last updated 2026-10-24)