菜单
Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/athola/claude-night-market --skill mission-orchestrator命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
基于 SOC 职业分类
正在显示 SKILL.md
| name | mission-orchestrator |
| description | Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow. |
| alwaysApply | false |
| category | workflow-orchestration |
| tags | ["mission","orchestrator","lifecycle","full-cycle","automation"] |
| dependencies | ["attune:project-brainstorming","attune:project-specification","attune:project-planning","attune:project-execution","attune:war-room-checkpoint","attune:war-room","leyline:risk-classification","leyline:damage-control","leyline:additive-bias-defense","imbue:justify","imbue:vow-enforcement","abstract:friction-detector"] |
| tools | [] |
| provides | {"workflow":["mission-lifecycle","state-detection","phase-routing","session-recovery","reflexion-buffer","trust-tier","adaptive-constraints"]} |
| usage_patterns | ["full-cycle-development","mission-resume","phase-routing"] |
| complexity | advanced |
| model_hint | deep |
| estimated_tokens | 600 |
| progressive_loading | true |
| modules | ["modules/mission-types.md","modules/state-detection.md","modules/phase-routing.md","modules/mission-state.md","modules/plan-review.md","modules/plan-versioner.md","modules/feedback-collector.md","modules/context-injector.md","modules/iteration-governor.md","modules/reflexion-buffer.md","modules/trust-tier.md","modules/adaptive-constraints.md"] |
| references | ["references/mission-charter.md","references/progress-report.md"] |
| role | entrypoint |
Wraps the entire attune development lifecycle (brainstorm → specify → plan → execute) into a single mission with automatic state detection, type selection, and phase routing. Follows the "persistent presence lens" pattern from spec-kit:speckit-orchestrator: delegates entirely to existing skills via Skill() calls, never re-implements phase logic.
/attune:brainstorm, /attune:specify, etc.)1. State Detection
Scan for existing artifacts (project-brief.md, specification.md, etc.)
|
2. Mission Type Selection
Auto-detect type based on artifacts, or accept user override
|
3. Phase Routing Loop
For each phase in the mission type:
a. Pre-phase validation (check prerequisites)
b. Invoke Skill(attune:{phase-skill})
c. Post-phase artifact check (verify output exists)
d. Post-phase backlog triage (create GitHub issues
for out-of-scope items after brainstorm/specify)
e. Update mission state
f. User checkpoint (skippable with --auto)
g. Error handling via leyline:damage-control
|
4. Completion
All phases complete, final state saved
| Type | Phases | Auto-detected When |
|---|---|---|
full| brainstorm → specify → plan → execute |
| No artifacts exist |
standard | specify → plan → execute | docs/project-brief.md exists |
tactical | plan → execute | docs/specification.md exists |
quickfix | execute | docs/implementation-plan.md exists |
See modules/mission-types.md for full type definitions and custom type support.
| Phase | Skill Invoked | Artifact Produced |
|---|---|---|
| brainstorm | Skill(attune:project-brainstorming) | docs/project-brief.md |
| specify | Skill(attune:project-specification) | docs/specification.md |
| plan | Skill(attune:project-planning) | docs/implementation-plan.md |
| execute | Skill(attune:project-execution) | Implemented code and tests |
The orchestrator never re-implements phase logic. Each phase is a complete Skill() invocation that handles its own workflow.
Missions persist state to .attune/mission-state.json. On resume:
See modules/mission-state.md for the state schema and recovery protocol.
The plan-to-execute transition uses an interactive review loop instead of a simple checkpoint. Plans are reviewed section by section, revised based on feedback, and must pass a mandatory war-room gate before execution.
Key capabilities:
See modules/plan-review.md for the full protocol.
The orchestrator parses the user's command-args and
free-text at mission start for natural-language trust
signals. Phrases like "ignore scope guard", "ultrathink",
"don't keep asking", and "be autonomous" are recognized
as directive overrides that adjust the constraint
profile without requiring an explicit
--constraints= flag.
Directive overrides win over mission-type defaults but never bypass the Safety Floor (pre-commit hooks, proof-of-work evidence, destructive-operation confirmation, external-facing actions). When a directive is detected, the orchestrator acknowledges it once at mission start and stops asking for the corresponding checkpoints. Repeated approval-seeking after a directive override is itself a workflow bug.
See modules/adaptive-constraints.md "User Directive
Override" section for the parsing table.
Define mission boundaries using the structured template from
references/mission-charter.md. A Mission Charter specifies:
See references/mission-charter.md for the full template and
examples.
Track progress with structured checkpoints using
references/progress-report.md. Generate reports at:
See references/progress-report.md for the template and
checkpoint rhythm guidance.
trust-tier.md when directive overrides are
active.This skill declares progressive_loading: true. To keep the
orchestrator's resident token cost minimal, load only the
subset of modules each mission type actually needs. The
orchestrator itself loads only the four core modules at
mission start; the rest are loaded on-demand when their
phase runs.
| Mission type | Core | Plan-review | Reflexion | Trust and adaptive |
|---|---|---|---|---|
quickfix (execute only) | yes | -- | -- | if directive |
tactical (plan -> execute) | yes | yes | if revising | if directive |
standard (specify -> plan -> execute) | yes | yes | if revising | if directive |
full (brainstorm -> specify -> plan -> execute) | yes | yes | yes | if directive |
Token cost (approximate, computed from wc -w on hub +
loaded modules and converted at ~1.3 tokens per word):
| Mission type | Loaded modules | Approx tokens |
|---|---|---|
quickfix | hub and core (4) | ~4,100 |
tactical | hub, core, and plan-review (9) | ~6,900 |
standard | same as tactical (9) | ~6,900 |
full | hub, core, plan-review, and reflexion (10) | ~7,900 |
The previous load-all pattern brought in roughly 10,100
tokens for every mission, including quickfix runs that
only need the execute phase. With per-type loading, quickfix
is ~60% lighter and the standard / tactical / full paths
save 22-32%.
When a directive override fires, the trust-tier + adaptive-constraints pair adds ~2,200 tokens on top of the mission-type baseline.
Skill(attune:project-brainstorming) - Brainstorm phaseSkill(attune:project-specification) - Specify phaseSkill(attune:project-planning) - Plan phaseSkill(attune:project-execution) - Execute phaseSkill(attune:war-room-checkpoint) - Risk assessment for RED/CRITICAL tasksSkill(leyline:risk-classification) - Task risk classificationSkill(leyline:damage-control) - Error recovery during phases/attune:mission - Invoke this skill/attune:mission --resume - Resume from saved state/attune:mission --type tactical - Override mission type.attune/mission-state.json