mission-brief
Skill145 starsChanged 23 days agoMITView on GitHub
Use when a mission brief must become verified work end to end — brief, then specify, clarify, plan, implement, verify, converge in one lane-carrying DAG with Default plus Speckit, Superpowers, Matt, and Addy lanes.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- tylerjrbuell/Wardenstheir own version, first seen Nov 15, 2026
- sunholo-data/ailangtheir own version, first seen Nov 13, 2026
- thanatchon36/skillstheir own version, first seen Oct 15, 2026
- sumo91/mission-brieftheir own version, first seen Sep 5, 2026
- Cloudscockpit/voltron-lions-claudecodetheir own version, first seen Sep 2, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sunholo-data/ailang★ 38same name
- sumo91/mission-brief★ 14same name
- Cloudscockpit/voltron-lions-claudecode★ 3same name
- tylerjrbuell/Wardens★ 2same name
- thanatchon36/skills★ 0same name
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 repository48 other files it gives its agents.
- architect-analyzeSkill
- architect-bootSkill
- architect-clarifySkill
- architect-implementSkill
- architect-initSkill
- architect-specifySkill
- writing-skillsSkill
- change-bootSkill
- change-clarifySkill
- change-initSkill
- change-publishSkill
- change-specifySkill
- evals-analyzeSkill
- evals-clarifySkill
- evals-implementSkill
- evals-initSkill
- evals-specifySkill
- evals-validateSkill
- factory-cleanSkill
- factory-initSkill
- factory-intentSkill
- factory-learnSkill
- factory-missionSkill
- factory-orchestratorSkill
- factory-queueSkill
- factory-releaseSkill
- factory-reviewSkill
- factory-runbookSkill
- factory-setupSkill
- factory-ticketsSkill
- product-analyzeSkill
- product-bootSkill
- product-clarifySkill
- product-implementSkill
- product-initSkill
- product-roadmapSkill
- product-specifySkill
- team-bootSkill
- team-constitutionSkill
- team-diagnoseSkill
- team-discoverSkill
- team-initSkill
- team-levelupSkill
- team-repairSkill
- team-setupSkill
- team-skillsSkill
- workspaceSkill
- tech-radar-bootSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 7 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
When ADLC_RUN_ID is not set, a person is in this session, and nothing else will answer a gate.
- Very specific: line 19
Before ending your turn, the run is completed, failed or aborted, or it is paused at a gate the person has been asked about.
- Very specific: line 37
Check specify CLI availability (specify --help on PATH).
- Distinctive: line 38
Look at repo usage hints (framework-native artifacts: specs dirs, plans dirs, spec-linked issues) — but a hint is never selection evidence …
- Distinctive: line 48
Default lane built into this skill.
- Distinctive: line 50
Read the intake: in a factory run the issue ref, otherwise the spec description from arguments.
- Very specific: line 52
Write spec.md: outcome, constraints, non-goals, acceptance criteria, and out of scope.
- Very specific: line 57
Write plan.md: the files table, the test-first order, and the risk notes for anything that could invalidate that order.
- Very specific: line 58
Write the failing suite first, based on spec.md, with tests/ as the only writable surface and source mounted read-only.
- Very specific: line 60
Write the minimum code with source as the only writable surface and tests/, spec.md and plan.md mounted read-only.
- Distinctive: line 146
No worktree: isolation belongs to the orchestrator.
- Distinctive: line 147
No lease: never acquire, renew or release a run lease.
- Distinctive: line 148
No tracker writes: no comments, labels, status transitions, or MR/PR creation.
- Distinctive: line 149
No merge or approval: this skill never approves, merges or ships.
“Common” is measured: kept by at least 6 in 10 of the 5 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
mission-brief
Scope rule: scripts stay skill-local — never source a script from another skill. For another skill's operations, invoke that skill (e.g.
architect-clarify,product-clarify,team-boot) via the Skill tool; for its documents, follow theRequiresline.scripts/andreferences/below are relative to this skill.{REPO_ROOT}denotes the project root (where.adlc/lives).
Requires: the factory-runbook skill (provides the publish procedure and run contracts): adlc-cli skills add tikalk/adlc-team-skills --skill factory-runbook.
In a local session — you answer the gates
When ADLC_RUN_ID is not set, a person is in this session, and nothing else will answer a gate. The agentic-container runtime that relays gates to Slack exists only in a runner pod.
- A paused run is your turn, not the end of the mission. When
adlc-cli workflow runorresumeexits with the run paused at a gate (run_paused,status: pausedinadlc-cli workflow state show <run_id>), ask the person the gate's question and options. Then runadlc-cli workflow resume <run_id> --input <verdict_input>=<answer>and keep going. Never end your turn on a paused run that nobody was asked about. - Every gate that approves MRs is followed by a step that opens them. A
gatewhose message promises MRs/PRs is followed by apublishstep:run-branch.shandopen-mr.shfor each repository the change touches, writingmr_url(mr_urlsfor more than one). Only then comes the write-back step, so the completion comment links real MRs. A gate with nothing after it to act on its answer is a plan defect; fix the plan before you start the run. - Before ending your turn, the run is
completed,failedor aborted, or it is paused at a gate the person has been asked about.
What this skill does
mission-brief owns the mission lifecycle end to end as one DAG: it turns the mission's brief into a spec whose acceptance criteria each answer yes or no, into an ordered plan, into tested code, into a converge verdict — judged against the brief, never against the implementer's claims. It works under the shared executor contract (invoke the factory-runbook skill; contract at references/executor.md in that skill): the brief step emits the Mission Brief draft per references/mission-brief-template.md; specify reads brief.md and emits a draft; clarify reads spec.md and emits a decision; plan reads spec.md plus the clarify decision and emits plan.md; test reads spec.md and emits an artifact-ref; code reads that test artifact plus spec.md and plan.md; verify reads the test and code artifacts and emits severity-ranked findings; converge reads brief.md and emits one verdict of DONE, CONTINUE, or SPEC_CORRECTION_NEEDED. A SPEC_CORRECTION_NEEDED verdict routes to the owning clarify gate, never to code.
The lane-carrying sections below keep one pointer per framework lane; the lane prose lives in its own home and is linked, never duplicated here. Lane resolution is a session instruction (Phase 0), never a script or table lookup.
Lane routing
The single lane table is references/lane-routing.yml (data, not prose): the five resolvable lanes (embedded, speckit, superpowers, matt, addy) and the seven lifecycle steps with their output_type/reads_from contract. Every resolvable lane has a section below; a lane without a section here can never be resolved.
Framework lane detection (Phase 0 — session-LLM instruction)
There is no detector script and no precedence table to run. In the brief step, inspect the well-known install paths yourself and disclose what you found in the brief:
- Inspect the installed skill packs via the Skill tool (distinctive names:
*speckit*,*superpowers*,*addy*,*matt*,*pocock*). - Inspect the plugin entries (the agent registry's plugin list — superpowers-style plugin installs live outside the skills dirs).
- Check
specifyCLI availability (specify --helpon PATH). - Look at repo usage hints (framework-native artifacts: specs dirs, plans dirs, spec-linked issues) — but a hint is never selection evidence on its own.
Resolution: the installed framework wins; usage hints among installed frameworks break ties only. Usage hints with no installed framework disclose and fall back to Default. Write the outcome into the brief exactly as:
Framework lane: <lane> (<evidence>)
where <lane> is one of embedded, speckit, superpowers, matt, addy, and <evidence> names what was inspected (installed:<pack>, plugin:<entry>, specify-cli, usage hints <paths>, not installed, or default).
Default lane (embedded)
Default lane built into this skill.
- Read the intake: in a factory run the issue ref, otherwise the spec description from arguments. Write the Mission Brief per
references/mission-brief-template.md: Goal, Constraints, Non-Goals, Success Criteria with a measurement method each, plus theFramework lanedisclosure. - Restate every success criterion as a binary, measurable outcome — each one answers a yes/no question through a command that exits, an artifact that exists, or a diff that shows the change.
- Write
spec.md: outcome, constraints, non-goals, acceptance criteria, and out of scope. Each acceptance criterion stays traceable to the success criterion it restates. Specify never selects technologies and never plans files; those belong to the plan and code steps. - Surface any criterion that cannot be measured and any constraint that conflicts with another; do not paper over either in prose.
- Resolve each surfaced item at the clarify phase — ask the person in a gated run, or in autonomous mode record the decision with its basis. The resulting decision is the
clarifyoutput. - Treat the spec's acceptance criteria as the plan's definition of done. List every file to create or modify, each with a one-line purpose. Order the work so each step leaves the tree valid — no step relies on a later step to make it correct or runnable.
- Name the exact test command that will prove the change, and put the test-first order ahead of the implementation steps.
- Write
plan.md: the files table, the test-first order, and the risk notes for anything that could invalidate that order. - Write the failing suite first, based on
spec.md, withtests/as the only writable surface and source mounted read-only. - Run it — the RED gate requires that at least one test fails before any implementation exists. A suite that passes immediately means the behavior exists or the assertions are empty: stop and route to the owning clarify gate for spec correction. Record the failing count in the run log.
- Write the minimum code with source as the only writable surface and
tests/,spec.mdandplan.mdmounted read-only. - Run the suite — the GREEN gate requires the full suite passes before converge. A failure loops back to the code step with the failure list attached; the loop is bounded by the mission's code-step retry cap and does not consume the converge circuit breaker. The code step never weakens the tests to pass the suite.
- Skip the split only when the run declares no test surface:
tdd: false, docs/config-only work, or interactive mode. A code-bearing step in autonomous or supervised mode never skips it. - Judge the built work against
brief.md, not the implementer's claims — re-run the suite, inspect the diff, confirm non-goals untouched. The converge judge works frombrief.mdand the non-goals, never from the verifier's own findings. - Emit severity-ranked findings: Critical, Important, Minor, each tied to evidence in the diff, suite output, or an untouched non-goal.
- Return one converge verdict:
DONEwhen criteria are met and the quality threshold is reached,CONTINUEwhen in-scope gaps remain,SPEC_CORRECTION_NEEDEDwhen a criterion is unmeasurable or scope conflicts. RouteSPEC_CORRECTION_NEEDEDto the owning clarify gate, never to code; returnCONTINUEto the implementation phase with findings attached. Never approve or merge; approval and merge stay human in the deploy phase.
Speckit lane
This section translates the shared lifecycle DAG into the speckit framework workflow; speckit keeps its own loop internals and the step contract below remains authoritative. All artifacts are committed directly to the repository under the specs/ tree, giving developers reviewing the pull request the native speckit audit trail.
- The
specifystep maps to the spec creation preset atgithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.specify.md, run through thespecifyCLI (specify bundle install adlc-spec-kit). It reads the brief and writes thespecs/intake (spec.md) scaffolded via.specify/templates. Shared contract:output_typedraftwithreads_frombrief.md. - The
clarifystep maps togithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.clarify.mdvia thespecifyCLI, resolving open questions and encoding decisions back intospec.md. Shared contract:output_typedecisionwithreads_fromspec.md. - The
planstep maps to the plan preset atgithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.plan.mdrun through thespecifyCLI, generatingspecs/architecture design (plan.md) alongside the dependency-ordered task breakdown fromgithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.tasks.mdintotasks.md. It reads.specify/templates and the clarified spec. Shared contract:output_typedraftwithreads_fromspec.md, clarify. - The
teststep maps to the TDD tasks command atgithub.com/tikalk/adlc-spec-kit-bundle/extensions/adlc-tdd/commands/tasks.md, which detects language and generates risk-plus-increment tests. It readsspec.mdand stages the failing suite intests/under the RED gate. Shared contract:output_typeartifact-refwithreads_fromspec.md. - The
codestep maps to the implementation preset atgithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.implement.md, executed through the RED-GREEN-REFACTOR cycle ofgithub.com/tikalk/adlc-spec-kit-bundle/extensions/adlc-tdd/commands/implement.md. It writes code tosrc/until the full suite passes under the GREEN gate. Shared contract:output_typeartifact-refwithreads_fromtest, spec.md, plan.md. - The
verifystep maps to the evaluation-driven verification command atgithub.com/tikalk/adlc-spec-kit-bundle/extensions/edd/commands/verify.md, running deterministic checks and quality assessments againstspecs/and.specify/grammar. Shared contract:output_typefindingswithreads_fromtest, code. - The
convergestep maps togithub.com/tikalk/adlc-spec-kit-bundle/presets/agentic-sdlc/commands/adlc.spec.converge.mdvia thespecifyCLI, judging the built work againstbrief.mdand returning the loop verdict (DONE,CONTINUE, orSPEC_CORRECTION_NEEDED). Shared contract:output_typedecisionwithreads_frombrief.md.
Canonical home: speckit framework integration.
Superpowers lane
This section translates the shared lifecycle DAG into the superpowers framework workflow across coding agents (Claude Code, Cursor, Codex, OpenCode, Gemini, etc.); superpowers keeps its own inner loop discipline and the step contract below remains authoritative. All design and planning artifacts are stored directly in the repository under docs/superpowers/ (specs/ and plans/), matching the native superpowers convention.
- The
specifystep maps to the design workflow ofgithub.com/obra/superpowers/skills/brainstorming, activated when the superpowers plugin or skill pack is installed (in the coding agent's configuration or atgithub.com/obra/superpowers/skills/brainstorming). It readsbrief.mdand writes the design specification underdocs/superpowers/specs/(spec.md). Shared contract:output_typedraftwithreads_frombrief.md. - The
clarifystep maps to the builder-check validation and targeted clarifying questions ofgithub.com/obra/superpowers/skills/brainstorming, resolving requirements and encoding confirmed decisions intospec.md. Shared contract:output_typedecisionwithreads_fromspec.md. - The
planstep maps togithub.com/obra/superpowers/skills/writing-plans, producing an implementation plan with bite-sized tasks underdocs/superpowers/plans/(plan.md). It readsspec.mdand clarified decisions. Shared contract:output_typedraftwithreads_fromspec.md, clarify. - The
teststep maps togithub.com/obra/superpowers/skills/test-driven-development(Iron Law: no production code without a failing test first), authoring tests intests/and staging them under the RED gate before code is touched. Shared contract:output_typeartifact-refwithreads_fromspec.md. - The
codestep maps togithub.com/obra/superpowers/skills/subagent-driven-development(orgithub.com/obra/superpowers/skills/executing-plans), executing the tasks until the full test suite passes under the GREEN gate. Shared contract:output_typeartifact-refwithreads_fromtest, spec.md, plan.md. - The
verifystep maps togithub.com/obra/superpowers/skills/verification-before-completionandgithub.com/obra/superpowers/skills/requesting-code-review, gathering fresh execution evidence and code review findings. Shared contract:output_typefindingswithreads_fromtest, code. - The
convergestep maps togithub.com/obra/superpowers/skills/finishing-a-development-branch, judging the built work againstbrief.mdand returning the loop verdict (DONE,CONTINUE, orSPEC_CORRECTION_NEEDED). Shared contract:output_typedecisionwithreads_frombrief.md.
Canonical home: superpowers framework integration.
Matt lane
This section translates the shared lifecycle DAG into the mattpocock/skills framework workflow across coding agents (Claude Code, Cursor, Codex, OpenCode, Gemini, etc.); matt keeps its modular discipline while the step contract below remains authoritative. Design, task, and review artifacts are stored in linked tracker spec issues and run-local drafts (spec.md, plan.md).
- The
specifystep maps to the design workflow ofgithub.com/mattpocock/skills/skills/engineering/to-spec, activated when the skill pack is installed (in its checkout or installed via the Skill tool). It readsbrief.mdand conversation, publishing a linked tracker spec issue or writingspec.md. Shared contract:output_typedraftwithreads_frombrief.md. - The
clarifystep maps to the alignment and boundary analysis ofgithub.com/mattpocock/skills/skills/engineering/grill-with-docs(andgrilling), resolving requirements and domain models intospec.md. Shared contract:output_typedecisionwithreads_fromspec.md. - The
planstep maps togithub.com/mattpocock/skills/skills/engineering/to-tickets, decomposing the spec into tracer-bullet tickets or task plans (plan.md). It readsspec.mdand clarified decisions. Shared contract:output_typedraftwithreads_fromspec.md, clarify. - The
teststep maps togithub.com/mattpocock/skills/skills/engineering/tdd(red-green-refactor loop), authoring failing tests staged under the RED gate before code is touched. Shared contract:output_typeartifact-refwithreads_fromspec.md. - The
codestep maps togithub.com/mattpocock/skills/skills/engineering/implement(andcodebase-design), implementing deep modules until the full suite passes under the GREEN gate. Shared contract:output_typeartifact-refwithreads_fromtest, spec.md, plan.md. - The
verifystep maps togithub.com/mattpocock/skills/skills/engineering/code-review(two-axis review: standards and spec fidelity), gathering fresh execution evidence and review findings. Shared contract:output_typefindingswithreads_fromtest, code. - The
convergestep maps togithub.com/mattpocock/skills/skills/engineering/prgates, judging built work againstbrief.mdand returning the loop verdict (DONE,CONTINUE, orSPEC_CORRECTION_NEEDED). Shared contract:output_typedecisionwithreads_frombrief.md.
Canonical home: matt framework integration.
Addy lane
This section translates the shared lifecycle DAG into the addyosmani/agent-skills framework workflow across coding agents (Claude Code, Cursor, Codex, OpenCode, Gemini, etc.); addy keeps its own checklist and constraint discipline while the step contract below remains authoritative. Design, task, and quality artifacts are stored under repository constraints files, tasks/ (plan.md, todo.md, spec.md), and references/ checklists (definition-of-done.md, testing-patterns.md, security-checklist.md).
- The
specifystep maps to the design workflow ofgithub.com/addyosmani/agent-skills/skills/spec-driven-developmentandgithub.com/addyosmani/agent-skills/skills/constraint-driven-development, activated when the agent-skills pack is installed (in its checkout or installed via the Skill tool). It readsbrief.mdand repo quality standards, writing the specification totasks/spec.md(orspec.md) and recording non-negotiables into the repository constraints log. Shared contract:output_typedraftwithreads_frombrief.md. - The
clarifystep maps to the ambiguity and boundary analysis ofgithub.com/addyosmani/agent-skills/skills/doubt-driven-development(andinterview-me), resolving requirements, checking edge cases, and recording confirmed decisions intospec.mdand quality constraints. Shared contract:output_typedecisionwithreads_fromspec.md. - The
planstep maps togithub.com/addyosmani/agent-skills/skills/planning-and-task-breakdown, sizing tasks and checking acceptance criteria againstreferences/definition-of-done.md, outputting structured task plans totasks/plan.md(ortasks/todo.md). It readsspec.mdand clarified decisions. Shared contract:output_typedraftwithreads_fromspec.md, clarify. - The
teststep maps togithub.com/addyosmani/agent-skills/skills/test-driven-development(aligned withreferences/testing-patterns.md), authoring tests intests/and staging them under the RED gate before code is touched. Shared contract:output_typeartifact-refwithreads_fromspec.md. - The
codestep maps togithub.com/addyosmani/agent-skills/skills/incremental-implementation(andgithub.com/addyosmani/agent-skills/skills/code-simplification), implementing thin vertical slices insrc/until the full test suite passes under the GREEN gate. Shared contract:output_typeartifact-refwithreads_fromtest, spec.md, plan.md. - The
verifystep maps togithub.com/addyosmani/agent-skills/skills/code-review-and-quality(evaluated againstreferences/security-checklist.md,references/performance-checklist.md, andreferences/accessibility-checklist.md) andgithub.com/addyosmani/agent-skills/skills/browser-testing-with-devtools, gathering fresh execution evidence and code review findings. Shared contract:output_typefindingswithreads_fromtest, code. - The
convergestep maps togithub.com/addyosmani/agent-skills/skills/shipping-and-launchverification gates, evaluating acceptance criteria and constraints againstbrief.mdand returning the loop verdict (DONE,CONTINUE, orSPEC_CORRECTION_NEEDED). Shared contract:output_typedecisionwithreads_frombrief.md.
Canonical home: addy framework integration.
Step contract
| Step | phase_type | output_type | reads_from | artifact |
brief | generate | draft | intake | brief.md |
specify | generate | draft | brief.md | spec.md |
clarify | clarify | decision | spec.md | — |
plan | generate | draft | spec.md, clarify | plan.md |
test | build | artifact-ref | spec.md | tests/ |
code | build | artifact-ref | test, spec.md, plan.md | src/ |
verify | verify | findings | test, code | — |
converge | verify | decision | brief.md | — |
Gates
- RED gate — after
test. The suite is run before any implementation exists, with source mounted read-only. RED passes only when at least one test fails, and the failing count is recorded in the run log. A suite that passes immediately means the behavior already exists or the assertions are empty: the gate fails and the run routes to the owning clarify gate for spec correction instead of advancing tocode. - GREEN gate — after
code. The suite is run again withtests/,spec.mdandplan.mdmounted read-only. GREEN passes only when the full suite passes. Any failure returns the failure list to thecodestep, bounded by the mission's code-step retry cap, and that loop-back does not consume the converge circuit breaker — only broken iterations do. The code step never weakens the tests to pass. convergeverdict — DONE, CONTINUE, SPEC_CORRECTION_NEEDED.DONE— acceptance criteria met and quality threshold reached.CONTINUE— in-scope gaps remain; findings return to implementation and the circuit breaker applies.SPEC_CORRECTION_NEEDED— a criterion is unmeasurable or scope conflicts; the verdict routes to the owning clarify gate, never to code. The converge judge works frombrief.mdand the non-goals, never from the verifier's own findings.convergeis never reached with a red suite: GREEN is the last mechanical check before verification, and a red run stops at the gate.- The split is skipped only when the run declares no test surface:
tdd: false, docs/config-only work, or interactive mode.
Boundaries
- No worktree: isolation belongs to the orchestrator; this skill works in the tree it is handed.
- No lease: never acquire, renew or release a run lease.
- No tracker writes: no comments, labels, status transitions, or MR/PR creation.
- No merge or approval: this skill never approves, merges or ships.
- Routes back: an unmeasurable criterion or a conflicting constraint stays at clarify until resolved; a spec later proven wrong is corrected through the owning clarify phase, never by quietly editing acceptance criteria downstream; an ambiguous or contradictory spec routes to its owning clarify phase; an implementation discovery that invalidates the order revises the plan; a
SPEC_CORRECTION_NEEDEDverdict routes to the owning clarify gate, never to code. - The comment bus is the durable inter-agent memory: every step publishes its terminal output (decisions, findings, artifact references — never drafts) as a structured marker comment on the PR/MR/issue. The next step reads previous markers before starting. Local files carry the same outputs for same-session runs.
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.

