Design
owainlewis/blueprintWrites a clear design for a proposed feature or system change. Use when important product or technical choices must be settled before coding. Covers behavior, interfaces, failures, risks, acceptance criteria, and tests. Use architecture to explain the current system.
At a glance
git clone --depth 1 https://github.com/owainlewis/blueprint
cp -r blueprint/skills/design ~/.claude/skills/design
Setup, runtime and requirements describe owainlewis/blueprint, the repo this skill ships in.
Also in owainlewis/blueprint
View the repoExplains how an existing system works today. Use for architecture maps, audits, or ARCHITECTURE.md. Return a chat report unless the user ask...
Reviews a technical proposal before implementation. Use for designs, RFCs, ADRs, architecture proposals, and issues that define how a system...
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use...
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, v...
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve name...
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or usef...
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, a...
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tic...
Proves that a code change meets its acceptance criteria. Uses focused automated checks and a real browser for browser-facing work. Use to te...