원클릭으로 Manus에서 모든 스킬 실행

marshail-delegate-to-knowledge-maintain

스타4

포크0

업데이트2026년 7월 9일 15:59

Maintain the MARSHAIL knowledge layer. Delegate when the user asks to "update the knowledge tree from this diff / commit range", "promote learnings from learn/inbox/", "rescan the knowledge tree", "refresh stale knowledge files", "split oversize topics", "sweep the knowledge layer", "update knowledge after this implementation cycle", "after the Learn stage promote inbox items into canonical files". Modes — `from-changes` (after an implementation cycle that changed code), `from-learning` (after the Learn stage), `rescan` (full sweep). The subagent (curator) updates topic files and indexes, splits oversize topics into sub-indexes recursively, respects autonomy mode, and returns a short summary of what changed (a full diff only in `review` mode).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

crestreach

crestreach/marshail

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

marshail-delegate-to-knowledge-maintain

Delegate this to the marshail-knowledge-curator subagent in mode from-changes, from-learning, or rescan. Do not inline the workflow — the agent owns it.

Call contract

Subagent: marshail-knowledge-curator
Mode: one of from-changes | from-learning | rescan
Pass (request-specific only):
- The intent (what knowledge update is wanted), always.
- from-changes: a list of changed paths or a git diff range.
- from-learning: paths to the inbox items to promote.
- rescan: nothing extra — operates on the whole tree vs HEAD.
- The agent reads .marshail/config.yml, the knowledge contract / implementation, and the indexes itself — do not pass them.
Expect back: a summary of what changed (counts: created / updated / removed / flagged) — not the full knowledge diff.
On result: under knowledge.autonomy: auto (default) it is already applied — read the summary. Under review, approve the diff. For larger restructures, escalate to marshail-delegate-to-knowledge-rebuild.

이 저장소의 다른 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-knowledge-maintain

description

marshail-delegate-to-knowledge-maintain

Delegate this to the marshail-knowledge-curator subagent in mode from-changes, from-learning, or rescan. Do not inline the workflow — the agent owns it.

Call contract

Subagent: marshail-knowledge-curator
Mode: one of from-changes | from-learning | rescan
Pass (request-specific only):
- The intent (what knowledge update is wanted), always.
- from-changes: a list of changed paths or a git diff range.
- from-learning: paths to the inbox items to promote.
- rescan: nothing extra — operates on the whole tree vs HEAD.
- The agent reads .marshail/config.yml, the knowledge contract / implementation, and the indexes itself — do not pass them.
Expect back: a summary of what changed (counts: created / updated / removed / flagged) — not the full knowledge diff.
On result: under knowledge.autonomy: auto (default) it is already applied — read the summary. Under review, approve the diff. For larger restructures, escalate to marshail-delegate-to-knowledge-rebuild.