一键在 Manus 中运行任何 Skill

marshail-delegate-to-plan

星标4

分支0

更新时间2026年7月9日 15:59

MARSHAIL Plan / shape stage — MANDATORY for every MARSHAIL change. Delegate whenever the user asks to "plan this change", "make a delivery plan", "produce delivery-plan.md", "shape the work", "break this into phases / packets / steps", "decide L1 / L2 / L3 / L4 depth", "decide PR boundaries", "decide rollout boundaries", "mark parallelizable work", "deepen the plan for phase X", "replan phase Y", or simply "let's plan". Also delegate at the start of any MARSHAIL change once the earlier stages (Specification through Architecture) are agreed (or skipped), and mid-change to deepen a previously high-level phase before its implementation cycle. The subagent picks the shallowest workable depth unless the user pins a target depth, and chooses a timing mode (full / staged / mixed).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

crestreach

crestreach/marshail

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

marshail-delegate-to-plan

Delegate this to the marshail-planner subagent. Do not inline the workflow — the agent owns it.

Call contract

Subagent: marshail-planner
Pass: whichever upstream artifacts exist (specification.md, change-brief.md, repo-recon.md, architecture-notes.md); planning timing mode (full | staged | mixed) if the user has a preference; target depth if pinned (e.g. "L2", "L4 in P1, L2 elsewhere"); existing delivery-plan.md if deepening / amending.
Expect back: approved delivery-plan.md (Scope line + Planning mode + Target depth, then phases / packets / steps to the agreed depth), plus logs/stage-5-plan.changelog.md and learning/stage-5-plan.learning.md.
On result: confirm approval and hand off to marshail-delegate-to-implement (Implement stage). For staged deepening, re-invoke this delegate before each implementation cycle of a still-shallow phase.

The Plan stage is mandatory in MARSHAIL — every change has a plan, even a single phase with one step.

同仓库更多 Skills

同仓库

marshail-delegate-to-implement

crestreach/marshail

MARSHAIL Implement stage. Delegate when the user asks to "implement phase X", "work on packet Y", "code this packet", "execute the plan", "start the next implementation cycle", "do the work for the current target", "write the code + tests for this", "run a Dev-QA pass", "close this cycle". Also delegate after the Plan stage (plan approved) to drive each implementation cycle, and after a verifier failure or reviewer fixup loop to resume coding. The subagent picks the cycle target, confirms / deepens the plan, executes (code + tests + Dev-QA where possible), offers the human a chance to inspect and give feedback, and closes the cycle by updating plan status, changelog, and learning files.

2026-07-094

marshail-promote-assets

crestreach/marshail

Copies MARSHAIL durable assets — both built-in lifecycle assets under `.marshail/{skills,skills-fallback,agents,rules}/` and repo-specific extensions under `.marshail/extensions/{skills,agents,rules}/` — into the project's config-sync source tree (default `.agent-config/`, overridable via `sync.agent_config_dir`), so the next `agent-conf-sync` run fans them out to all tool layouts. Names are preserved as-is: built-ins keep their `marshail-` prefix, extensions keep their `mx-` prefix. Use when the user asks to "promote MARSHAIL skills/agents/rules", "promote MARSHAIL extensions", "copy from .marshail to .agent-config", "wire MARSHAIL assets into the sync source", or similar — and from `marshail-init` for first-time setup.

2026-07-094

marshail-delegate-to-analysis

crestreach/marshail

MARSHAIL Repo recon / analysis stage. Delegate when the user asks to "analyze the repo for this change", "do recon", "narrow the search surface", "find the likely files / services / contracts", "identify invariants and test seams", "produce repo-recon.md", "what touches X in this codebase?", "where does Y live?", "scope the code areas before planning". Also delegate when change-brief.md exists and the Analysis stage is in scope, or when a planner / implementer flags they don't know enough about an area. The subagent reads the brief and existing knowledge, walks likely paths, and returns a tight repo-recon.md plus a stale-knowledge list — keeping intermediate exploration out of the parent context.

2026-07-094

marshail-delegate-to-architecture

crestreach/marshail

MARSHAIL Architecture / design stage. Delegate when the user asks to "design the solution", "agree the implementation concept", "discuss the architecture", "propose components / modules / APIs / schemas", "produce architecture-notes.md", "draft an ADR for this", "what's the right shape for this?", "compare design tradeoffs", "high-level layout for this change". Also delegate when change-brief.md and repo-recon.md exist and the change is large enough that the solution shape isn't obvious yet. The subagent drives the design conversation, captures rationale, and (when significant) promotes durable decisions to ADRs.

2026-07-094

marshail-delegate-to-driver

crestreach/marshail

Run a whole MARSHAIL change end-to-end. Delegate when the user asks to "run MARSHAIL on this", "do a full MARSHAIL change for X", "orchestrate this change end-to-end", "drive this through MARSHAIL stages", "manage stage transitions for me", "resume this MARSHAIL change", "pick up where the change left off", "I want one orchestrator instead of juggling stages", or any high-level "do the whole thing under MARSHAIL" intent. Also delegate when starting a new change in a MARSHAIL repo (with `.marshail/` initialized) and the user wants per-stage approval gates managed automatically. The subagent agrees scope, detects current stage from on-disk artifacts, dispatches per-stage agents, and surfaces approval gates.

2026-07-094

marshail-delegate-to-help

crestreach/marshail

MARSHAIL on-demand help. Delegate when the user asks "how does MARSHAIL work?", "what does the X stage do?", "which skill / agent should I use next?", "what stage am I in?", "explain the knowledge layer", "how do I write a delivery plan?", "what goes in repo-recon.md?", "how does the config sync fit in?", "what's the difference between marshail-init and marshail-load?", "what's the marshail acronym?", "MARSHAIL?", or any procedural / conceptual question about the MARSHAIL process, the knowledge layer, the available skills / agents, or how MARSHAIL applies to the current change. Also delegate when the caller is unsure which skill / agent to use, or when another skill / agent encounters a MARSHAIL-meta question that would pollute its context. The subagent reads marshail.md and the repo's .marshail/ tree, returns a concise answer, and (when asked) hands off — read-only.

2026-07-094

name

marshail-delegate-to-plan

description

marshail-delegate-to-plan

Delegate this to the marshail-planner subagent. Do not inline the workflow — the agent owns it.

Call contract

Subagent: marshail-planner
Pass: whichever upstream artifacts exist (specification.md, change-brief.md, repo-recon.md, architecture-notes.md); planning timing mode (full | staged | mixed) if the user has a preference; target depth if pinned (e.g. "L2", "L4 in P1, L2 elsewhere"); existing delivery-plan.md if deepening / amending.
Expect back: approved delivery-plan.md (Scope line + Planning mode + Target depth, then phases / packets / steps to the agreed depth), plus logs/stage-5-plan.changelog.md and learning/stage-5-plan.learning.md.
On result: confirm approval and hand off to marshail-delegate-to-implement (Implement stage). For staged deepening, re-invoke this delegate before each implementation cycle of a still-shallow phase.

The Plan stage is mandatory in MARSHAIL — every change has a plan, even a single phase with one step.