mission-brief
Mission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when you want an end-to-end specify → plan → implement ↔ converge loop with gates, a circuit breaker, resume, and an audit trail — without YAML files or per-framework profiles.
tikalk · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add tikalk/adlc-team-skills --skill mission-brief技能说明
name: mission-brief description: >- Mission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when you want an end-to-end specify → plan → implement ↔ converge loop with gates, a circuit breaker, resume, and an audit trail — without YAML files or per-framework profiles.
mission-brief
What this skill does
mission-brief takes a feature description, structures it into a Mission
Brief (goal, constraints, success criteria), generates an ordered step
list with prompts, and executes those steps — each step dispatched to a
subagent whose prompt triggers the installed SDD skills. No YAML workflow
files, no per-framework profiles, no profile detection. The step prompts use
canonical SDD terminology (specify, plan, implement, converge) that works with
any SDD skill set — model-invoked skills auto-trigger, command-based
frameworks match by filename, and if neither exists the subagent executes
directly.
When to use
- "Build this feature end to end": you give a description, mission-brief composes the pipeline and runs specify → plan → implement ↔ converge.
- You want a converge loop with a circuit breaker and an audit trail.
- You want to resume an interrupted mission across sessions
(
mission-brief --resume). - You want to run unattended across sessions (
mission-brief --async).
When NOT to use
- A single small edit — just do it; a mission is overhead.
- You already have a spec and tasks and only want to implement one task — invoke the implement skill directly.
Mission Brief template
Before generating steps, the description is structured into:
## Mission Brief
**Goal**: <what to build — one sentence>
**Constraints**: <tech stack, limitations, dependencies, requirements>
**Non-Goals**: <what is explicitly out of scope — e.g., "no database storage, local memory cache only">
**Success Criteria**:
- <measurable outcome 1>
- <measurable outcome 2>
- <measurable outcome 3>
The brief serves two purposes:
- Forces explicit done-criteria upfront — feeds the converge step's independence check (the checker verifies against these criteria).
- Carries mission context into every step's delegation prompt so each subagent has full context without re-reading prior steps.
Inputs
$ARGUMENTS
The text in the $ARGUMENTS block above IS your mission description —
proceed with it immediately. Do not ask the user what they want to build.
Parse flags from the arguments first, then treat the remaining text as
spec_description:
--async/--sync— execution mode flag (overrides config default).--resume— explicit resume from state.- Everything else — the mission description (
spec_description).
If no description and not --resume: derive a best-effort description from the
feature name (git branch, or the last state's feature). If --resume and no
state: report "No interrupted mission found" and stop.
Feature name derivation: slugify the description to lowercase-hyphenated,
drop stop words (a, an, the, new, to, with, for, add, fix, update). Example:
"add a new react dashboard with telemetry" → react-dashboard-telemetry.
If .adlc/workflow/runs/ already contains a dir with that name, append -2,
-3, etc.
Flow
All paths are relative to the current working directory (the project root where the agent operates). Do not look in subdirectories for config or state unless explicitly stated.
Phase 0 — Configuration
mkdir -p .adlc/workflow(and.adlc/workflow/tmp,.adlc/workflow/runs).- If
.adlc/workflow/workflow-config.ymldoes not exist, copy it from the skill'sconfig-template.yml(located alongside this SKILL.md). - Read
.adlc/workflow/workflow-config.yml. Defaults if fields are absent:
workflow:
execution: sync # sync | async
supervision: gated # gated | hybrid | autonomous
max_iterations: 5
max_spec_corrections: 2
circuit_breaker: 3
quality_threshold: null # optional 0-100, blocks DONE below threshold
# models: { strong: "...", fast: "..." } # optional
Resolve the effective execution mode: --async/--sync flag > config
execution > sync. If --async and supervision is gated/hybrid: warn
("async forces ungated; running autonomous") and treat as autonomous for
this run.
Phase 1 — Resume check (--resume only)
<FEATURE_DIR>=.adlc/workflow/runs/<feature>/(defined in Phase 4, but referenced here for the completed-mission check).
If --resume was passed:
- Read
.adlc/workflow/.mission-state.json. - If
<FEATURE_DIR>/mission-log.jsonexists → report "Mission already completed for feature X. Audit trail: …" → stop. - If state exists with non-empty
completed_steps→ resume: load the step list fromstate.steps, skip to Phase 5 (Execute) at the first incomplete step. - If no state → report "No interrupted mission found. Run
mission-brief \"<desc>\"to start one." → stop.
If --resume was NOT passed and a state file with non-empty completed_steps
exists: ask — "An interrupted mission for feature X exists (N/M steps
done). Run mission-brief --resume to continue, or confirm to start fresh
(this discards the state)." Do not silently clobber.
Phase 2 — Mission Brief
Structure spec_description into the Mission Brief template:
- Goal: extract the core objective in one sentence.
- Constraints: infer tech stack, limitations, and requirements from the
description and the project context (check
package.json,go.mod, language files, existing specs). If unclear, leave a placeholder and mark it for the user to fill. - Non-Goals: infer 1–2 reasonable boundari