dev
Skill0 starsChanged 28 days agoMITView on GitHub
Implement one planned task bundle as the Dev role: read the contract, change only touch_files, run the machine-checkable DoD, fill 02-dev-workspace.md and hand off to QA. Use when a task contract exists and you are assigned implementation. Do not use for planning, task slicing, architecture, or QA verification.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- waynesutton/convexskillstheir own version, first seen Nov 15, 2026
- waynesutton/builder-skillstheir own version, first seen Nov 15, 2026
- ztcools/skillstheir own version, first seen Nov 15, 2026
- mayoz/rabbittheir own version, first seen Nov 15, 2026
- DataArt/artisyn-implementation-harnesstheir own version, first seen Nov 15, 2026
- inancgumus/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use metrics-graphana, control-flow and 9 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.
slopusSkillmetrics-graphana
Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.
Also in 3 projects that use this
slopusSkillcontrol-flow
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
Also in 3 projects that use this
MicrosoftSkillsessions
Core principles and workflow router for changes to the Agents Window under src/vs/sessions.
Also in 3 projects that use this
AnthropicSkilloffice-hours
Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.
Also in 3 projects that use this
nicepkgSkillteam
根据任务快速组建临时 AI Agent 团队协作。自动从 .claude/agents/ 中选择最合适的成员组队。
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 5 projects that use this
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- slopus/happy★ 25ksame name
- microsoft/playwright-cli★ 15ksame name
- atopile/atopile★ 4ksame name
- cexll/myclaude★ 2.8ksame name
- waynesutton/markdown-site★ 628same name
- Automattic/wordpress-activitypub★ 583same name
- waynesutton/builder-skills★ 404same name
- waynesutton/convexskills★ 404same name
- justrach/merjs★ 357same name
- stella/stella★ 274same name
44 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- changeSkill
- convergeSkill
- diagnose-windows-sandbox-aclSkill
- plan-linterSkill
- prd-generatorSkill
- qaSkill
- quality-engineeringSkill
- reviewSkill
- spec-generatorSkill
- task-decompositionSkill
- test-engineeringSkill
- diagnose-windows-sandbox-aclSkill
- changeSkill
- convergeSkill
- devSkill
- plan-linterSkill
- prd-generatorSkill
- qaSkill
- quality-engineeringSkill
- reviewSkill
- spec-generatorSkill
- task-decompositionSkill
- test-engineeringSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 2 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
No edits to 01-contract.md, 03-qa-verification.md, 04-process.md or tests/acceptance/ (including *.feature files and step definitions).
- Very specific: line 54
Confirm scope and BDD contract: Read 01-contract.md frontmatter and Section 4 Gherkin scenarios.
- Very specific: line 58
Prepare the work and isolate the branch: Check git rev-parse --abbrev-ref HEAD.
- Very specific: line 63
Read dod.feature_file only to understand acceptance semantics.
- Very specific: line 80
Hand off to QA: Only when every self-verification item passes and complexity limits are satisfied, change - [ ] WAITING_FOR_QA to - [x] …
- Very specific: line 83
On rework: Read QA's failure traces in 03-qa-verification.md, fix only within the contract, re-run the DoD, update 02 for the new attempt …
- Distinctive: line 107
Missing or contradictory contract: stop; report the field and ask the Planner to fix it.
- Very specific: line 108
Branch guard or acceptance ownership conflict: stop; never edit/commit on main/master and never author *.feature files or step definitions …
- Very specific: line 116
Tooling unavailable: use the project's manual commands and record evidence in 02.
- Distinctive: line 134
If QA requests rework, update the deviation table for the new attempt.
“Common” is measured: kept by at least 6 in 10 of the 36 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
Dev — Task Implementation
Implement one task bundle and hand it to QA. This skill defines the process and carries its own
role boundaries in references/role-boundaries.md. If the adopting
repository defines agent rules (AGENTS.md, a role-rules directory or equivalent), read and follow
them when present; the skill never grants extra access.
Use when
- A task under
tasks/<task-id>/has a completed01-contract.mdand you are the Dev role. - You need to implement a vertical slice, run its DoD commands, record evidence and hand off.
- You are reworking a task after QA issued
REWORK_REQUIRED.
Do not use when
- The contract is missing, incomplete or contested — return it to the Planner.
- You are asked to plan, slice or review tasks, or to verify another agent's work.
- The requested change is outside the contract's
touch_files— escalate or split the task.
Inputs
tasks/<task-id>/01-contract.md— authoritative YAML frontmatter,touch_files,dod, Section 4 Gherkin behavioral scenarios (Given-When-Then invariants), the acceptance feature file declared indod.feature_file, and inherited ADRs. Dev readsdod.feature_filefor acceptance semantics but must never author or edit*.featurefiles or step definitions;tests/acceptance/is QA-owned.- Spec anchors referenced by the contract.
- Project commands for type check and lint, the existing test suite, and the QA-owned acceptance
target declared in
dod.test_file(the BDD runner entrypoint, never the.featurefile). tasks/<task-id>/02-dev-workspace.md— the blank form you fill.
Outputs
- Code changes only for paths listed in
touch_files. - Code adhering to BDD invariants and cyclomatic complexity limits ($V(G) \le 10$ standard, warning
$11-15$ justified in
02, critical $> 15$ prohibited). - A completed
02-dev-workspace.mdwith metadata, actual changes, self-verification, and the Implementation deviations table (rowsDEV-001,DEV-002, ... or an explicit None row). - Exactly one handoff marker:
- [x] WAITING_FOR_QA, checked only when every DoD item passes. - No edits to
01-contract.md,03-qa-verification.md,04-process.mdortests/acceptance/**(including*.featurefiles and step definitions).
Workflow
- Confirm scope and BDD contract. Read
01-contract.mdfrontmatter and Section 4 Gherkin scenarios. Check thattask_idequals the directory name, and thattouch_files,dod(test_file,feature_file),adherence_adrsand Given-When-Then invariants are defined. Report missing or contradictory items to the Planner. - Prepare the work and isolate the branch. Check
git rev-parse --abbrev-ref HEAD; never edit or commit onmain/master; derive/switch tofeat/<task-id>(ortask/<task-id>) and record it in02-dev-workspace.md. Do not reopen an already accepted task unless a reviewer reopens it. - Implement vertical slice under BDD and complexity limits. Change only files in
touch_files. Implement logic fulfilling the Given-When-Then invariants declared in Section 4 anddod.edge_cases. Readdod.feature_fileonly to understand acceptance semantics; never author or edit*.featurefiles or their step definitions. Control single-function cyclomatic complexity ($V(G) \le 10$ standard). If complexity approaches the warning limit ($11-15$), apply refactoring patterns (Extract Method, Strategy / Lookup Table, Guard Clauses). If $V(G) > 15$, refactor before proceeding. - Run machine-checkable DoD and self-verification. Execute
dod.type_checkanddod.lint, then run the project's existing tests; consider everydod.edge_casesitem. Self-audit cyclomatic complexity on all touched functions. The acceptance artifacts (dod.feature_file, its step definitions and thedod.test_filerunner target) are QA-owned: run them only if they already exist, never author or edit them. If they do not exist yet, record that in02and let QA run them during verification. Capture commands/results. - Fill
02-dev-workspace.md. Record branch, base/handoff commit, design notes, one row per actually changed file, net line counts, and tick each self-verification item that is true. Include explicit architectural justification for any function with warning complexity ($11 \le V(G) \le 15$). Leave items unticked if they did not pass. Complete the Implementation deviations table: one row per place where the code differs from the contract or spec (DEV-001,DEV-002, ...; operationadd|modify|remove; a#sec-*anchor), or write None in every cell when nothing deviated. - Hand off to QA. Only when every self-verification item passes and complexity limits are
satisfied, change
- [ ] WAITING_FOR_QAto- [x] WAITING_FOR_QA. That single checked box is the handoff trigger. Do not edit03or04. - On rework. Read QA's failure traces in
03-qa-verification.md, fix only within the contract, re-run the DoD, update02for the new attempt and hand off again. Escalate repeated failures instead of bypassing the contract.
Quality gate (before declaring done)
- Every changed path is listed in
01-contract.md→touch_files. - No file outside the blast radius was created or modified.
- The working tree is on the branch recorded in
02-dev-workspace.md; nothing was edited or committed onmain/master. - Implementation honors all Given-When-Then Gherkin scenarios and behavioral invariants.
- Type check and lint exit successfully; the project's existing tests pass.
- Cyclomatic complexity self-audit passes: all functions meet $V(G) \le 10$ (or $11-15$ with
justification in
02); none exceed $V(G) > 15$. - The QA-owned acceptance artifacts (
dod.feature_file, its step definitions and thedod.test_fileBDD runner target) are declared; none was authored or edited by Dev, and any not-yet-authored artifact is recorded for QA. - Every
dod.edge_casesitem has an implementation/test rationale. 02-dev-workspace.mdis complete for this attempt, including the Implementation deviations table (explicit None row when nothing deviated).- Only
WAITING_FOR_QAis checked;03and04are untouched.
Failure handling
- Missing or contradictory contract: stop; report the field and ask the Planner to fix it.
- Branch guard or acceptance ownership conflict: stop; never edit/commit on
main/masterand never author*.featurefiles or step definitions — escalate instead of bypassing the boundary. - Out-of-scope change needed: split the task or escalate; never edit outside
touch_files. - DoD command missing or not runnable: report it with the command and error; do not hand-wave the check.
- DoD fails: fix the implementation and rerun. Do not tick the handoff box while a check fails.
- Complexity exceeds threshold ($V(G) > 15$): refactor using Extract Method, Strategy / Lookup Table, Guard Clauses, or State patterns before handoff; never hand off critical complexity.
- Tooling unavailable: use the project's manual commands and record evidence in
02; the workflow must not depend on optional tooling.
04-process.md and tooling
04-process.md is derived output. After the handoff checkbox is checked, optional repository
tooling appends HANDOFF_QA_REQUESTED and updates macro_status/current_lock_holder. Never
hand-edit 04; without tooling, rely on git/CI and the checked box.
After QA_PASSED: spec write-back ownership
The Implementation deviations table is Dev's last deliverable for the task. After QA records
QA_PASSED, the converge skill owns the spec write-back: it folds the confirmed deviations into
.specs/02-tech-spec.md, archives the task bundle and closes the change proposal.
- Dev never edits
.specs/02-tech-spec.mdand never archives the bundle. - A structural deviation (new component, changed boundary, new ADR-level decision) is escalated to
the Planner/
spec-generatorinstead of being converged silently. - If QA requests rework, update the deviation table for the new attempt; do not pre-write spec prose.
References
references/dev-protocol.md— detailed checklists, scope verification, McCabe cyclomatic complexity limits, refactoring patterns, handoff and rework procedure.- Role boundaries:
references/role-boundaries.md— write scope, read-only scope, invariants and the honest enforcement model (bundled; no external files needed). - Repository rules: read
AGENTS.mdand any role-rules files when the adopting project defines them; they may add requirements but are not required for this skill to work. - Task bundle format:
task-decompositionskill (optional sibling; this skill only consumes its artifacts).
Honest limits
This skill does not grant write access and cannot enforce role isolation. Where the repository has CI (for example a git-based role audit) or branch protection, that is the authoritative layer. The contract, not this document, defines the allowed blast radius.
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.

