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.
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.
About
Reviews
Write a reviewNo 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
- 0.471score
interrogate
puukis
Socratic requirement clarification — one question at a time before any planning or code.
SkillCFreshness: CClaude Code +9 - 0.471score
orchestrate
puukis
Intelligent task routing — evaluates complexity and asks the user whether to handle in the main session or dispatch to specialist sub-agents.
SkillCFreshness: CClaude Code +9 - 0.469score
changelog
puukis
Generate a CHANGELOG.md entry from git log since last tag — invoked via /changelog
SkillCFreshness: CClaude Code +9 - 0.469score
debrief
puukis
End-of-session structured reflection — what worked, what broke, what to do differently.
SkillCFreshness: CClaude Code +9 - 0.469score
debug
puukis
Systematic root cause analysis — reproduce, isolate, hypothesize, verify before any fix
SkillCFreshness: CClaude Code +9 - 0.469score
docs
puukis
Writes accurate documentation by reading source first — never invents API signatures
SkillCFreshness: CClaude Code +9 - 0.469score
engineer
puukis
Writes production-ready code — reads patterns first, runs tests after, no gold-plating
SkillCFreshness: CClaude Code +9 - 0.469score
forget
puukis
Delete structured learnings or legacy observations from lstack memory.
SkillCFreshness: CClaude Code +9 - 0.469score
guard
puukis
Enable maximum safety workflow by combining careful safety mode with a freeze edit boundary.
SkillCFreshness: CClaude Code +9 - 0.469score
learn
puukis
Manually store a typed, trust-aware structured learning in lstack.
SkillCFreshness: CClaude Code +9 - 0.469score
architect
puukis
System design before any code is written — invoked via /architect; produces ADRs and ARCHITECTURE.md
SkillCFreshness: CClaude Code +9 - 0.469score
careful
puukis
Enable opt-in warnings or denials for risky Bash commands in the current Claude Code session.
SkillCFreshness: CClaude Code +9
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
- Repository
- github.com/puukis/lstack
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from puukis
- 0.471score
orchestrate
puukis
Intelligent task routing — evaluates complexity and asks the user whether to handle in the main session or dispatch to specialist sub-agents.
SkillCFreshness: CClaude Code +9 - 0.471score
interrogate
puukis
Socratic requirement clarification — one question at a time before any planning or code.
SkillCFreshness: CClaude Code +9 - 0.469score
changelog
puukis
Generate a CHANGELOG.md entry from git log since last tag — invoked via /changelog
SkillCFreshness: CClaude Code +9 - 0.469score
debug
puukis
Systematic root cause analysis — reproduce, isolate, hypothesize, verify before any fix
SkillCFreshness: CClaude Code +9 - 0.469score
docs
puukis
Writes accurate documentation by reading source first — never invents API signatures
SkillCFreshness: CClaude Code +9 - 0.469score
debrief
puukis
End-of-session structured reflection — what worked, what broke, what to do differently.
SkillCFreshness: CClaude Code +9
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.
Cite this page
blueprint skill. Agent Mart. https://agentmart.dev/skills/puukis-blueprint (last updated 2026-10-24)