youtube-tutorials
Code and examples from my YouTube channel tutorials.
4 skills11 commands+1419
@owainlewisDevelopment
Plugin
blueprint
Gives coding agents focused skills for turning a rough idea into reviewed work: checking a technical proposal before coding, designing the system architecture, and delivering tested pull requests through review and gated merges.
Plugin Signal73/100Solid
maintained98
capable52
documented75
adopted56
Claude Code
$ npx -y skills add owainlewis/blueprint --agent claude-code
Codex
$ npx skills add owainlewis/blueprint -a codex
Cursor
$ npx skills add owainlewis/blueprint -a cursor
Gemini CLI
$ npx skills add owainlewis/blueprint -a gemini-cli
GitHub Copilot
$ npx skills add owainlewis/blueprint -a github-copilot
OpenCode
$ npx skills add owainlewis/blueprint -a opencode
Windsurf
$ npx skills add owainlewis/blueprint -a windsurf
What's inside
11 Skills
/architecture-reviewReviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that would make it wrong, unsafe, or impossible to prove, and the open questions that block building it./architectureWrites root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment./codex-issue-coordinatorCoordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch./html-docGenerates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser./improveMakes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions./planSplits a spec into small tasks, each a working slice an agent can finish in one pull request. Use when a spec is too big for one PR, or to create tracker tickets.
README
Blueprint
Senior engineering habits for coding agents.
Small skills for Claude Code and Codex that turn an idea into a reviewed, tested pull request.
Quick start · Our take · The workflow · Verification · Example
Our take
As models get smarter, skills get simpler.
Agents already know how to write code. What they lack is the judgment that experienced engineers bring to a team: write down what you are building before you build it, prove it works, and get someone else to check it. Blueprint encodes those habits, drawn from years of engineering experience and working with some of the best engineers in the world.
So each skill is short. It gives the agent three things and trusts it with the rest:
| A template | The shape of a good PRD, spec, or pull request. A template beats a page of instructions. |
| A standard of proof | Every check passes, every acceptance criterion has a test, and the tests fail when the code is reverted. |
| A second pair of eyes | A fresh reviewer, ideally a different model, checks the work against the spec before a human sees it. |
The same skills work in Claude Code and Codex.
Quick start
1. Install
npx skills add owainlewis/blueprint
2. Describe the product. Ask your agent:
Use /requirements for a CRM that helps a small consulting firm track leads and follow-ups.
You get REQUIREMENTS.md: the PRD, written as user stories with checkable outcomes.
3. Spec one feature.
Use /spec for capturing a new lead.
You get docs/capture-lead/spec.md: the user journeys for that feature, a diagram, the technical design an agent can build from, and the decisions behind it.
4. Ship it.
Use /task-to-pr for docs/capture-lead/spec.md.
The agent builds it, runs every check until green, gets an independent review, waits for CI, fixes what comes back, and leaves a pull request ready for you.
See the full result in the consulting CRM example.
Design, plan, build, verify
Blueprint follows how good engineers already work. Each skill belongs to one stage.
flowchart LR
D["Design<br/>/requirements /architecture /spec"] --> P["Plan<br/>/plan"]
P --> B["Build<br/>/task-to-pr"]
B --> T["Test<br/>does it work?"]
T -->|fails| B
T --> R["Review<br/>is it right?"]
R -->|findings| B
R --> M(["Merge"])
subgraph V [Verify]
T
R
end
Skip any stage the work does not need. A small, clear fix can go straight to Build.
Verify has two parts, in order. Test asks does it work?: machines run format, lint, typecheck, tests, and browser checks. Review asks is it right?: another model, then you, check that it matches the spec, is safe, and can be maintained. Review starts only once tests pass. The verification guide shows how to set up both in any repository.
Design
| Skill | Use it when | You get |
|---|---|---|
/requirements | Starting a product or changing what it does | REQUIREMENTS.md, a PRD of user stories |
/architecture | Designing the system or changing its shape | ARCHITECTURE.md with a data flow diagram |
/spec | A feature has decisions to settle first | User journeys, a diagram, technical design, decisions, acceptance checks |
/architecture-review | A design choice is costly to get wrong | Findings and a verdict before any code |
/html-doc | You want to share a design as a web page | A checked, static HTML view |
Plan
| Skill | Use it when | You get |
|---|---|---|
/plan | A spec is too big for one pull request | Small tasks, each a working slice |
Build
| Skill | Use it when | You get |
|---|---|---|
/task-to-pr | A spec or task is ready to build | A tested, reviewed pull request, left open unless you say "and merge it" |
/codex-issue-coordinator | You have a batch of GitHub issues for Codex | One worker and one checked PR per issue |
/improve | Code works but is hard to follow | Simpler code with the same behavior |
Verify
| Skill | Use it when | You get |
|---|---|---|
/test | You need to know it works | Every check green, and pass or fail for each criterion |
/review | You need to know it is right | Spec fit, correctness findings, and a verdict from a fresh reviewer |
/task-to-pr runs Test and Review for you, then waits for CI.
Opt-in by design
Blueprint runs only when you ask for it. "Fix this bug" gets your agent's normal behavior; "use /task-to-pr to fix this bug" gets the full workflow. Once you pick a workflow, it loads the skills it needs on its own.
Claude Code honors this through disable-model-invocation: true, and Codex
through agents/openai.yaml. Agents only merge when you ask them to, or when you
invoke /codex-issue-coordinator by name.
Guides
- Verification: set up testing and review for any repository.
- Choosing a skill: where each skill starts and stops.
- Workflows: small fixes, larger features, existing systems, and issue batches.
- Consulting CRM example: requirements, architecture, a spec, and a plan.
- Migration: upgrading from an older Blueprint.
- Changelog
Project
Blueprint stays small on purpose. It is not an issue tracker, an agent runtime, or a release system. Read CONTRIBUTING.md before opening a pull request, and report security problems through SECURITY.md.
Released under the MIT License.
Stars on GitHub
Momentum
- stars in total
- 432
File tree
More plugins by @owainlewis.
View @owainlewis’s profile@owainlewismachinist
A Claude Code skill for creating, assigning, and monitoring software tasks through Machinist's GitHub issue workflow, intake labels, direct runs, and managed queue.
1 skill532
@owainlewisSimilar plugins.
skills
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
31 skills324k
@mattpococksuperpowers
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
15 skills1 hook311k
@obraecc
Gives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
200 skills71 agents1 MCP+3+2+2+2+2+2+2+1+1303k
@affaan-mreact
Developer tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
14 skills4 agents252k
@facebookQuestions about blueprint.
Install it with the command on its page. It includes architecture-review, architecture, codex-issue-coordinator. Its skills do not fire on their own yet. Free and open source.
- What is blueprint?
- owainlewis/blueprint is a plugin of skills and agents for coding work, covering architecture review, system design, and delivering reviewed pull requests. Use it when you want an agent to plan a change, validate a proposal, or ship code through a gated review workflow.
- How do I install blueprint?
- Run these in Claude Code: npx -y skills add owainlewis/blueprint --agent claude-code. Then prompt normally.
- Does blueprint auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin.
- Is blueprint free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
- Which coding agents can use blueprint's skills?
- blueprint installs in Claude Code, and its skills also install in Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI. Each skill's page has the install command. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it