Menu
Conductor-facing command to inspect and apply project scaffolding migrations from the canonical manifest (content/project-scaffolding.yml).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Agentic Engineering Protocol for Hermes - structured delegation model, risk classification, adversarial review loops, code quality gates, git workflow conventions, and named agent definitions. Load this skill when doing AI-assisted software development with Hermes Agent.
Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Pre-implementation technical design agent. Spawn when you need a structured technical plan before writing code. Reads the codebase, identifies patterns and constraints, evaluates approaches, and produces a concrete plan a Worker can execute directly. Never writes or modifies files.
General-purpose implementation agent. Spawn for any code change: new features, bug fixes, refactors, configuration changes, or script writing. Reads the codebase to understand conventions, implements the change, runs quality gates, and returns a clear summary of what was done. This is the standard Worker for all Elevated-risk implementation tasks.
Cheap per-turn stop-condition check for open-goal loops. Spawned by the conductor ONLY after an Elevated iteration produces a clean Skeptic sign-off, to evaluate the operator-declared goal_condition and return continue-vs-stop only - never for a Low/Trivial iteration (no Skeptic sign-off exists to run after; the conductor evaluates goal_condition directly there instead). Tier 1 (haiku) leaf agent - read-only, no subagent spawning, never runs in place of, before, or concurrently with a Skeptic review. Does NOT review correctness or safety and does NOT raise, waive, or comment on Skeptic findings. Returns BLOCKED only as a structural guard when spawned without a confirmed Skeptic sign-off; the conductor handles this BLOCKED as a fallback to direct evaluation, NOT as the generic Worker-BLOCKED-means-cap_reached-escalation semantics in content/references/subagent-protocol.md - a BLOCKED return here never halts the loop. On any other failure (unavailable, errored, timeout, malformed output) the conductor falls bac
| name | ds-migrate-project |
| description | Conductor-facing command to inspect and apply project scaffolding migrations from the canonical manifest (content/project-scaffolding.yml). |
| user-invocable | true |
Run the Activation preflight from
METHODOLOGY.mdbefore proceeding. If inactive, no-op and exit.
Inspect or apply project scaffolding migrations from the canonical manifest (content/project-scaffolding.yml). By default (no flags) runs a dry-run diff and shows what would change without applying anything.
/ds-migrate-project # dry-run, show diff, no apply
/ds-migrate-project --apply # apply additive rules
/ds-migrate-project --apply --include-destructive # apply additive + destructive (markers, file modifications, renames)
/ds-migrate-project --reset <version> # roll back scaffolding_version stamp only
Shells out to:
agentic-migrate diff [--manifest <resolved-path>] [--project-root <cwd>]
Prints a human-readable summary of what --apply would do. Read-only - no changes written.
Shells out to:
agentic-migrate apply [--manifest <resolved-path>] [--project-root <cwd>]
Applies additive scaffolding rules from the manifest:
.gitignore patterns (exact-line match after rstrip(); never duplicates)..agentic/ files from content/templates/ (never overwrites existing files).scaffolding_version in .agentic/config.json when all rules are satisfied..agentic/context.md if anything was written.~/.agentic/.scaffolding-apply.lock before writing (EWOULDBLOCK = another session active, skip silently).The markers: key in the manifest is IGNORED by this path. Operator-owned scaffolding (AGENTS.md markers, destructive file changes) requires --include-destructive.
Same as --apply plus applies the markers: section of the manifest. Currently a no-op because the v1 manifest has no markers. Future manifest versions may add markers for:
AGENTS.md (e.g. opt-in markers, tracker config).agentic/ filesUse this only when you understand and accept all the changes the manifest prescribes. Preview with the dry-run diff first.
Sets scaffolding_version in .agentic/config.json to the specified integer without undoing any applied changes.
Use case: you want the next preflight to re-run the full diff and re-emit the audit line - for example, to verify the migration engine is idempotent after a manual edit to .gitignore or .agentic/. Does NOT undo applied changes; if you need to undo, do so manually.
agentic-migrate apply --project-root <cwd> # after resetting stamp, re-apply to re-verify
agentic-migrate resolves the manifest in this order (first found wins):
AGENTIC_MANIFEST_PATH env var~/.claude/skills/agentic-engineering/project-scaffolding.yml<script_dir>/../content/project-scaffolding.yml (dev path)| Code | Meaning |
|---|---|
| 0 | Success / no-op |
| 1 | Drift detected (check subcommand only) |
| 2 | Manifest not found or parse error |
| 3 | Partial apply - some rules errored |
--apply. Only --include-destructive can touch AGENTS.md, and only when the manifest's markers: section contains instructions for it.scaffolding_version stamp in .agentic/config.json is the source of truth for "has this project been migrated to vN". The preflight Step 6 compares this stamp against the manifest version on every session start.