Document-assembly, pre-write invariant-guard, and atomic-write algorithm for forgeplan-map-pack's EMIT stage (RFC-023 Proposed Direction SS1 roster row 7 + Invariant #1; PRD-075 FR-5; SPEC-003 SS C0 the one-sentence contract, SS C3 gate G4). Covers: assembling meta/canvas/composition/zones/nodes/edges from the extraction+edges+composition inputs, the pre-write self-check trio RFC-023's own function signature assigns to this stage (no zone-cell overlap, every edge endpoint in nodes, every node.zone in zones -- independently re-derived afterward by the guardian's GC-2, NOT to be confused with SPEC-003's differently-numbered C1 INV-1/2/3 trio which this stage satisfies by disciplined passthrough construction instead), the reject-own-output-before-write rule, the exact tmp-rename atomic-write recipe mirroring map-guardian.mjs's own write, and the status:proposed + NEEDS_CONFIRM sentinel contract. Invoked by the map-emitter agent only. Triggers: "assemble map.json", "invariant guard before write", "atomic tmp-rena
Zone/node/mega-node extraction algorithm for forgeplan-map-pack's EXTRACT stage (RFC-023 Proposed Direction SS1 roster row 5, "THE HEART"; PRD-075 FR-3; SPEC-003 SS C1 INV-2, SS D4). Covers: the merge-then-dedup rule across the 3 scan scratch files, the content-hash node-id formula (sha1(kind+":"+path_or_slug)[:12], INV-2 -- never a label or counter), zone_hints binning with the z.core default-home fallback, why zone.cols is pinned from the composition and never derived from node count (append-stability), the GROUPED (per-kind) mega-node collapse rule for over-capacity zones (never one opaque zone-wide dump), and RU narration attachment into description_ru from real docs only. Invoked by the zone-extractor agent only -- not a general-purpose codebase-summarization skill. Triggers: "mint node id", "content-hash id formula", "zone binning", "mega-node collapse", "pin zone cols", "merge scan scratch files", "description_ru narration".
Edge trust-classification and grep-verification algorithm for forgeplan-map-pack's VERIFY stage (RFC-023 Proposed Direction SS1 roster row 6; PRD-075 FR-4; SPEC-003 SS D2 the 11 VALID_RELATIONS, SS D3 the typed-link/code-dep namespace default rule). Covers: the namespace classification rule, the exact 11-relation allowlist for typed-link edges, the mandatory Bash grep-verification pass for code-dep edges with the verified_by="grep:<pattern>" format map-guardian.mjs's XC-2 re-runs verbatim, the unconditional drop-if-unverified rule (never emit a code-dep edge as noise), and argv-safe grep discipline (no shell interpolation of untrusted pattern content). Invoked by the edge-verifier agent only. Triggers: "classify edge namespace", "verify code-dep edge", "grep verification pass", "11 valid relations", "drop unverified edge", "verified_by format".
Forgeplan structured engineering workflow — plan features, create PRD/RFC/ADR, check project health, route tasks to correct depth, review artifacts, think before coding. Triggers: forge, forgeplan, route task, create prd, check health, review artifact, activate, lifecycle, R_eff, evidence. Not for: simple bug fixes, formatting, trivial changes.
Live reference for the 66 mcp__forgeplan__* MCP tools and the 82 forgeplan CLI subcommands shipped in forgeplan 0.32.1. Agents and humans consult this skill when they know what they want to do (create an artifact, score a graph, dispatch sub-agents, detect anomalies) but don't yet know which tool name to call. Organised by use-case (lifecycle / discovery / quality / health / AI-driven / multi-agent / brownfield / activity / FPF / playbooks / plugins / release / safety) rather than alphabetically. Each section maps tools to canonical use-cases + which Profile A / B / C / D agent or which skill should call them. Includes known safety warnings (forgeplan#350 MCP body literal-string-only, forgeplan#348 score-all hint typo, forgeplan#351 plugins doctor install syntax). Triggers: "forgeplan tool reference", "which forgeplan command", "forgeplan-cookbook", "/forgeplan-cookbook", "what mcp tool", "how do I create artifact via mcp", "forgeplan cli vs mcp", "forgeplan capabilities"
Task-planning skill. Takes a SPECIFIC TASK as input (e.g., "refactor auth module", "ship payment service", "audit security of API gateway"), classifies it into one of 14 routing-map contexts, applies the matching methodology, and renders a structured Plan using templates/smith-plan.md. Dispatches the `smith` agent for routing decisions, returns a Plan markdown ready for orchestrator hand-off. Optionally creates a NOTE artifact to persist the Plan via forgeplan. Triggers: "smith plan", "/smith-plan", "спланируй задачу", "plan this task", "how should we approach", "как подойти к задаче"
Educational routing skill. Walks the user through smith's methodology routing matrix without committing to a specific task. Use to learn "when do I apply BMAD vs SPARC?", "what methodology for brownfield?", "explain the bug fix workflow". Pulls from routing-map.md (14 contexts + 29 methodology cards) and sections/NN-*.md (detailed playbooks). Output: educational comparison + recommendation when user describes their situation. Does NOT produce a Plan artifact — for that, use /smith-plan. Triggers: "smith routing", "/smith-routing", "explain methodology", "какая методология", "when do I use", "compare methodologies", "routing walkthrough", "BMAD vs SPARC", "Strangler Fig or rewrite", "show me the routing matrix"
Master-orchestrator entry-point. Reads project state (forgeplan_health, memory_recall, git), classifies context (1 of 14: greenfield / brownfield / feature / bug-fix / refactor / decision / audit / discovery / tech-debt / incident), applies methodology routing matrix, returns a structured Plan and recommends specialist-agent dispatches. Calls the `smith` agent for the planning + the routing-map.md for the brain. Default behaviour: status + recommend next step. Sub-modes via args: `bootstrap` (greenfield onboarding), `plan <task>` (per-task plan), `routing` (educational walkthrough), `status` (current state only). Triggers: "smith", "/smith", "кузнец", "что дальше", "куда идём", "возьми управление", "scrum master", "master orchestrator", "captain mode", "оркеструй", "take charge"