build
Skill65 starsChanged 7 months agoMITView on GitHub
Software development end-to-end: scope -> design -> plan -> execute -> deploy. Merges scope, writing-plans, executing-plans, and subagent-driven-development. Use when the user says 'build', 'implement', 'code', 'write a script', 'create a feature', or when /think chains here after identifying a concrete software deliverable.
- Commits and pushes
169 other projects use a version of this.
Adopted by
Most recently taken up by
- IntelRealSense/librealsensetheir own version, first seen Nov 16, 2026
- realsenseai/librealsensetheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- jayden-dang/skillstheir own version, first seen Nov 16, 2026
- colinc86/glosstheir own version, first seen Nov 16, 2026
- wald21x6-ops/builder-kittheir own version, first seen Nov 16, 2026
Used with
Projects with it also use backprop, finances and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JuliusBrusseeSkillbackprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Also in 4 projects that use this
GerardoRdz96Skillfinances
Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".
Also in 3 projects that use this
cpiprintSkillfavicon
Generate favicons from a source image
Also in 3 projects that use this
madeehahassanSkillGo-Live
Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.
Also in 3 projects that use this
TrevokeSkilldefine
Use when a new feature request, bug report, or work request needs requirements defined before implementation
Also in 3 projects that use this
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 6 projects that use this
Other versions169 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 169
- FalkorDB/FalkorDB★ 11ksame name
- realsenseai/librealsense★ 9.1ksame name
- IntelRealSense/librealsense★ 9.1ksame name
- microsoft/microsoft-ui-xaml★ 8.6ksame name
- NexaAI/nexa-sdk★ 8.5ksame name
- hathach/tinyusb★ 7.3ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- pytorch/TensorRT★ 3ksame name
159 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- debugSkill
- financial-advisorSkill
- generate-image-openaiSkill
- good-morningSkill
- pdfSkill
- planeSkill
- reply-xSkill
- researchSkill
- search-historySkill
- send-emailSkill
- simplify-julesSkill
- skill-creatorSkill
- stop-slopSkill
- thinkSkill
- watch-contactsSkill
- wrap-upSkill
- writeSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If standalone invocation: Run a lightweight scope pass.
- Distinctive: line 94
After each batch: present what was done, what changed, any issues encountered
- Distinctive: line 95
Wait for approval before proceeding to the next batch
- Distinctive: line 96
If a task fails: report the error, retry once if transient, stop and report if persistent.
- Distinctive: line 100
Only when [Your Name] explicitly says "just run it", "autonomous mode", or "don't wait for me."
- Distinctive: line 111
Run tests after implementation changes.
- Distinctive: line 118
Look up the project-specific deploy process:
- Distinctive: line 126
Verify after deploy: Check the live URL or service endpoint.
- Distinctive: line 128
If no deploy is needed (library code, internal tools), skip this step.
- Distinctive: line 135
Write a descriptive commit message
- Very specific: line 137
If the session is substantial, remind about /wrap-up
“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build
Software development end-to-end: scope -> design -> plan -> execute -> deploy -> ship. Handles the full lifecycle from "I want to build X" to "it's live and committed."
Arrives from: Direct invocation, or chained from /think when a concrete software deliverable is identified.
Step 0: Scope Verification
If arriving from /think: Requirements already exist (framing statement, constraints, minimum version). Confirm they're sufficient, then skip to Step 2.
If standalone invocation: Run a lightweight scope pass.
- What exactly are we building?
- Who uses it? (user, automated system, Jules)
- What's explicitly out of scope?
- What's the minimum version that delivers value?
Confirm scope before proceeding. One question at a time, with proposed answers. Don't frontload all questions -- ask, get the answer, then ask the next one.
Step 1: Existing Code Search
Dispatch a parallel Haiku Explore subagent to search for:
- Related code, existing utilities, patterns to reuse
- Project-level CLAUDE.md and config
- Similar implementations in the codebase
Present findings in 3-5 bullets. Don't re-research what was already found in /think.
Reuse over rebuild. Actively search for existing functions and utilities that can be reused. Never propose new code when a suitable implementation already exists in the codebase.
Step 2: Design
Architecture sketch: 3-5 bullets covering components, data flow, interfaces.
Identify dependencies, risks, and open questions. If major design decisions are needed, surface them as Decision Cards:
[DECISION] Summary | Rec: X | Risk: Y | Reversible? Yes/No
One-way doors get explicit approval before proceeding.
Design review. Dispatch a fresh Sonnet subagent with the design sketch. Prompt: "Are we building the right thing? Simpler approach? Edge cases? Missing tests? Feasibility?"
Self-review (run internally, surface only issues):
- Failure post-mortem: "3 months from now, this failed. What happened?"
- Over-engineering post-mortem: "3 months from now, this was massive overkill. What didn't we need?"
- Unstated assumptions: What are we assuming without acknowledging?
- Open questions: What would a skeptical reviewer ask?
Step 3: Plan
Break work into batches of 3-7 tasks each. A batch is a logical unit of work that can be reviewed as a set.
Each task includes:
- File: File to modify (or create)
- Action: What to do (specific action, not vague direction)
- Verify: How to confirm it worked (test command, expected output, visual check)
Task granularity: one action per 2-5 minutes (write test -> run it -> implement -> run again -> commit).
Save plan to both locations:
~/.claude/plans/YYYY-MM-DD-[description].mdDocuments/Field-Notes/Plans/YYYY-MM-DD-[description].md
Present plan for approval before executing.
Step 4: Execute
Two modes. Batch is default. Autonomous requires explicit opt-in.
Batch Mode (default)
- Execute one batch of tasks
- After each batch: present what was done, what changed, any issues encountered
- Wait for approval before proceeding to the next batch
- If a task fails: report the error, retry once if transient, stop and report if persistent. Don't silently swallow errors.
Autonomous Mode
Only when [Your Name] explicitly says "just run it", "autonomous mode", or "don't wait for me."
- Dispatch one subagent per independent task using
isolation: "worktree"for filesystem safety - Two-stage review per task:
- Stage 1 (spec compliance): Does the output match the task spec?
- Stage 2 (code quality): Is the code clean, tested, and consistent with project patterns?
- Continuous progress -- don't wait for human sign-off between tasks
- Report results when all tasks complete
Both modes
- Run tests after implementation changes. Don't leave broken code.
- Subagents cannot write to subdirectory repos (
Code/jules/,Code/kink-archetypes/). Main session handles those writes.
Step 5: Deploy
Look up the project-specific deploy process:
| Project | Deploy Command |
| [your-domain] | Scripts/push-[your-handle].sh |
| Quiz app | Scripts/deploy-quiz.sh |
| Other | Present the deploy command for review before running |
Verify after deploy: Check the live URL or service endpoint. "Deploy succeeded" is not the same as "it works."
If no deploy is needed (library code, internal tools), skip this step.
Step 6: Ship
- Stage specific files for commit (never
git add .or-A) - Write a descriptive commit message
git push- If the session is substantial, remind about
/wrap-up
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

