Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

marshail-init

Étoiles4

Forks0

Mis à jour22 juin 2026 à 20:52

First-time MARSHAIL setup in a repository. Assumes scripts/install-marshail.sh has placed the durable assets under .marshail/ (and can run it if not); then does the repo integration the install needs judgment for — merging the MARSHAIL entry-point into the repo's AGENTS.md, scaffolding and populating the .agent-config/ config-sync source via marshail-promote-assets, running the cyncia sync, updating .gitignore, and offering the initial knowledge bootstrap. Idempotent.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

crestreach

crestreach/marshail

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

marshail-init

description

marshail-init

Setup skill — runs once per repo, after the install script has placed MARSHAIL's files.

Division of labor (install vs. init)

scripts/install-marshail.sh owns installation. It downloads MARSHAIL at a ref and installs / updates the durable assets under .marshail/ (which include the canonical marshail.md) plus the repo-root LICENSE inside .marshail/, reconciles config.yml, writes .marshail/VERSION, and installs cyncia. It is idempotent — re-run it to update. This skill never re-copies those files — refer to the script (and README.md) for the install/update contract.
marshail-init (this skill) owns repo integration. The steps that need judgment and a human in the loop: wiring the MARSHAIL entry-point into the repo's AGENTS.md, scaffolding and populating the .agent-config/ config-sync source, running the sync, updating .gitignore, and bootstrapping knowledge.

By the time this skill can run, the install script has already placed it under .marshail/, so .marshail/ is present.

Prerequisites

A repo (any layout), fresh or with an existing top-level AGENTS.md.
.marshail/ installed by scripts/install-marshail.sh. If it is missing or partial, run the installer first (scripts/install-marshail.sh, or the install one-liner in the MARSHAIL project README); this skill can invoke it but does not reimplement it.

Inputs (read at start)

The repo root and any existing top-level AGENTS.md.
The installed .marshail/ (assets, config.yml, ENTRYPOINT.md, and the AGENTS.md entry-point snippet).
Existing .agent-config/ (or similarly named config-sync source) if present.
Existing .cyncia/ checkout if present.

Workflow

Confirm the install. Check for .marshail/ (and .marshail/marshail.md). If absent or incomplete, run scripts/install-marshail.sh (or ask the user to) — the script downloads and places everything and installs cyncia. Do not re-copy MARSHAIL files here.
Merge the MARSHAIL entry-point into the repo's AGENTS.md. Take the .marshail/AGENTS.md snippet and merge it into the repo's authoritative AGENTS.md — the root AGENTS.md in the direct layout, or .agent-config/AGENTS.md in the separate-source layout. Propose the merge for approval (per extensions.autonomy); do not silently overwrite user-authored content.
Decide on tool fan-out. If the user does not want their durable assets fanned out to tool-native layouts, skip to step 7 — MARSHAIL runs fine read-in-place from .marshail/.
Provision the .agent-config/ config-sync source (or whatever the user already calls it) if absent:
- .agent-config/AGENTS.md — the user's authoritative AGENTS.md (start from the merged snippet in step 2 if the user wants).
- .agent-config/{skills,agents,rules,mcp-servers}/ — empty directories with .gitkeep placeholders. See the sync tool's README for the source-tree format.
Promote MARSHAIL durable assets into .agent-config/ by running marshail-promote-assets. It copies the built-ins (skills/, skills-fallback/, agents/, rules/ — marshail- prefix) and the extensions (extensions/{skills,agents,rules}/ — mx- prefix) from .marshail/ into .agent-config/ as-is, keeping every name unchanged.
Run the sync (ask first). Invoke .cyncia/scripts/sync-all.sh -i .agent-config -o . to fan everything out into the tool-native layouts cyncia is configured to emit (the set is cyncia's, see .cyncia/cyncia.conf). Warn the user that the sync overwrites the generated directories on every run; only the source trees (.marshail/ + .agent-config/) are hand-edited.
Update .gitignore if the user agrees: ignore the generated tool-layout directories and generated root files (CLAUDE.md, .mcp.json), and the transient per-change working tree .marshail/work/ (the artifact chain is rebuilt per change; .marshail/archive/ is retained, so do not ignore it).
Offer the initial knowledge bootstrap. Trigger marshail-delegate-to-knowledge-init (curator init mode) to build the initial knowledge snapshot. This is not silent: it is offered as the final init step and the user can run it now or defer it to a later session. Under auto autonomy the curator writes the snapshot and returns a summary; under review it returns a diff for approval.

Outputs

The MARSHAIL entry-point merged into the repo's authoritative AGENTS.md.
(Optional) .agent-config/ scaffolded and populated with MARSHAIL durable assets (built-ins keep their marshail- prefix; extensions keep their mx- prefix).
(Optional) Tool-layout files written by the sync.
(Optional) Updated .gitignore.
An initial knowledge tree under .marshail/knowledge/ produced by the bootstrap (applied with a summary under auto, or a diff for approval under review) — unless deferred.

Exit criteria

.marshail/ is present (installed by the script) and the entry-point snippet is merged into the repo's authoritative AGENTS.md.
If the user opted in: .cyncia is installed, .agent-config/ exists, MARSHAIL assets are promoted into it, and the sync has run cleanly at least once.
Initial knowledge snapshot is created (applied under auto, or a diff approved under review) — or explicitly deferred to a later session.

Next steps

Updates / re-installs: re-run scripts/install-marshail.sh (idempotent) — it reconciles config.yml and refreshes the assets, marshail.md, and LICENSE without touching .marshail/knowledge/, .marshail/work/, or .marshail/marshail-override.md.
Promotion + sync (during init): marshail-promote-assets is invoked from step 5, followed by the cyncia sync in step 6.
Knowledge bootstrap (final step, opt-in): marshail-delegate-to-knowledge-init, which delegates to marshail-knowledge-curator in init mode with fresh context. Pass: path to .marshail/knowledge/ (empty) and any detected language / framework hints. In environments without subagent support, the fallback skill marshail-knowledge-init runs the same logic inline.

Plus depuis ce dépôt

même dépôt

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-init

description

marshail-init

Setup skill — runs once per repo, after the install script has placed MARSHAIL's files.

Division of labor (install vs. init)

scripts/install-marshail.sh owns installation. It downloads MARSHAIL at a ref and installs / updates the durable assets under .marshail/ (which include the canonical marshail.md) plus the repo-root LICENSE inside .marshail/, reconciles config.yml, writes .marshail/VERSION, and installs cyncia. It is idempotent — re-run it to update. This skill never re-copies those files — refer to the script (and README.md) for the install/update contract.
marshail-init (this skill) owns repo integration. The steps that need judgment and a human in the loop: wiring the MARSHAIL entry-point into the repo's AGENTS.md, scaffolding and populating the .agent-config/ config-sync source, running the sync, updating .gitignore, and bootstrapping knowledge.

By the time this skill can run, the install script has already placed it under .marshail/, so .marshail/ is present.

Prerequisites

A repo (any layout), fresh or with an existing top-level AGENTS.md.
.marshail/ installed by scripts/install-marshail.sh. If it is missing or partial, run the installer first (scripts/install-marshail.sh, or the install one-liner in the MARSHAIL project README); this skill can invoke it but does not reimplement it.

Inputs (read at start)

The repo root and any existing top-level AGENTS.md.
The installed .marshail/ (assets, config.yml, ENTRYPOINT.md, and the AGENTS.md entry-point snippet).
Existing .agent-config/ (or similarly named config-sync source) if present.
Existing .cyncia/ checkout if present.

Workflow

Confirm the install. Check for .marshail/ (and .marshail/marshail.md). If absent or incomplete, run scripts/install-marshail.sh (or ask the user to) — the script downloads and places everything and installs cyncia. Do not re-copy MARSHAIL files here.
Merge the MARSHAIL entry-point into the repo's AGENTS.md. Take the .marshail/AGENTS.md snippet and merge it into the repo's authoritative AGENTS.md — the root AGENTS.md in the direct layout, or .agent-config/AGENTS.md in the separate-source layout. Propose the merge for approval (per extensions.autonomy); do not silently overwrite user-authored content.
Decide on tool fan-out. If the user does not want their durable assets fanned out to tool-native layouts, skip to step 7 — MARSHAIL runs fine read-in-place from .marshail/.
Provision the .agent-config/ config-sync source (or whatever the user already calls it) if absent:
- .agent-config/AGENTS.md — the user's authoritative AGENTS.md (start from the merged snippet in step 2 if the user wants).
- .agent-config/{skills,agents,rules,mcp-servers}/ — empty directories with .gitkeep placeholders. See the sync tool's README for the source-tree format.
Promote MARSHAIL durable assets into .agent-config/ by running marshail-promote-assets. It copies the built-ins (skills/, skills-fallback/, agents/, rules/ — marshail- prefix) and the extensions (extensions/{skills,agents,rules}/ — mx- prefix) from .marshail/ into .agent-config/ as-is, keeping every name unchanged.
Run the sync (ask first). Invoke .cyncia/scripts/sync-all.sh -i .agent-config -o . to fan everything out into the tool-native layouts cyncia is configured to emit (the set is cyncia's, see .cyncia/cyncia.conf). Warn the user that the sync overwrites the generated directories on every run; only the source trees (.marshail/ + .agent-config/) are hand-edited.
Update .gitignore if the user agrees: ignore the generated tool-layout directories and generated root files (CLAUDE.md, .mcp.json), and the transient per-change working tree .marshail/work/ (the artifact chain is rebuilt per change; .marshail/archive/ is retained, so do not ignore it).
Offer the initial knowledge bootstrap. Trigger marshail-delegate-to-knowledge-init (curator init mode) to build the initial knowledge snapshot. This is not silent: it is offered as the final init step and the user can run it now or defer it to a later session. Under auto autonomy the curator writes the snapshot and returns a summary; under review it returns a diff for approval.

Outputs

The MARSHAIL entry-point merged into the repo's authoritative AGENTS.md.
(Optional) .agent-config/ scaffolded and populated with MARSHAIL durable assets (built-ins keep their marshail- prefix; extensions keep their mx- prefix).
(Optional) Tool-layout files written by the sync.
(Optional) Updated .gitignore.
An initial knowledge tree under .marshail/knowledge/ produced by the bootstrap (applied with a summary under auto, or a diff for approval under review) — unless deferred.

Exit criteria

.marshail/ is present (installed by the script) and the entry-point snippet is merged into the repo's authoritative AGENTS.md.
If the user opted in: .cyncia is installed, .agent-config/ exists, MARSHAIL assets are promoted into it, and the sync has run cleanly at least once.
Initial knowledge snapshot is created (applied under auto, or a diff approved under review) — or explicitly deferred to a later session.

Next steps

Updates / re-installs: re-run scripts/install-marshail.sh (idempotent) — it reconciles config.yml and refreshes the assets, marshail.md, and LICENSE without touching .marshail/knowledge/, .marshail/work/, or .marshail/marshail-override.md.
Promotion + sync (during init): marshail-promote-assets is invoked from step 5, followed by the cyncia sync in step 6.
Knowledge bootstrap (final step, opt-in): marshail-delegate-to-knowledge-init, which delegates to marshail-knowledge-curator in init mode with fresh context. Pass: path to .marshail/knowledge/ (empty) and any detected language / framework hints. In environments without subagent support, the fallback skill marshail-knowledge-init runs the same logic inline.