skills/arc-implementing/SKILL.md
Use when orchestrating large project implementation in a worktree
npx skillsauth add gregoryho/arcforge arc-implementingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrator for large projects. Automatically expands epic → features → tasks → execution.
Use when:
specs/<spec-id>/dag.yaml.arcforge-epic marker carries both epic and spec_id)specs/<spec-id>/epics/<epic-id>/epic.md or specs/<spec-id>/epics/<epic-id>/features/*.md presentDo not use when:
Implementer is the Orchestrator. It calls other skills and does not write code itself.
.arcforge-epic marker exists (supplies both epic and spec_id)specs/<spec-id>/epics/<epic-id>/epic.md / specs/<spec-id>/epics/<epic-id>/features/*.md presentarc-coordinating to sync from base and check blocked_by.blocked_by is not empty: STOP and use the blocked format.arc-writing-tasksspecs/<spec-id>/epics/<epic-id>/epic.mdspecs/<spec-id>/epics/<epic-id>/features/*.md)arc-writing-tasksspecs/<spec-id>/epics/<epic-id>/features/<feature>.mddocs/tasks/<feature>-tasks.mdarc-writing-tasks to refine. Max 2 refinement cycles — if still vague, escalate to human.arc-agent-driven| Phase | Skill | Input | Output |
|-------|-------|-------|--------|
| 0 | arc-coordinating | worktree | sync + blocked status |
| 1 | arc-writing-tasks | specs/<spec-id>/epics/<epic-id>/epic.md | features breakdown |
| 2a | arc-writing-tasks | specs/<spec-id>/epics/<epic-id>/features/<feature>.md | tasks file |
| 2b | arc-agent-driven | tasks file | completed code |
| 2b | arc-dispatching-parallel | (via arc-agent-driven, if review finds multiple issues) | parallel fixes |
| End | arc-finishing-epic | completed epic | merge decision |
─────────────────────────────────────────────────
✅ Epic complete: <epic-name>
Features implemented:
- feature-1: 4 tasks, all passing
- feature-2: 6 tasks, all passing
- feature-3: 3 tasks, all passing
Total: 13 tasks, 0 failures
Commits: 13
Next: Use arc-finishing-epic to decide merge/PR/keep/discard
─────────────────────────────────────────────────
─────────────────────────────────────────────────
⚠️ Implementer blocked: waiting for dependencies
Epic: <epic-name>
Blocked by: <dep-1>, <dep-2>
To resolve:
1. Complete blocking epics first
2. Run `arc-coordinating` sync from base
3. Verify `blocked_by` is empty
Then resume implementer
─────────────────────────────────────────────────
─────────────────────────────────────────────────
⚠️ Implementer blocked
Epic: <epic-name>
Feature: <feature-name>
Task: <task-id>
Issue: [description]
To resolve:
1. [action]
Then resume implementer
─────────────────────────────────────────────────
testing
Use when the user explicitly invokes `/arcforge:arc-auditing-spec <spec-id>` for a read-only advisory audit of an SDD spec family (design, spec, dag, decision anchors). Only triggered by direct user invocation; never auto-invoked from any pipeline skill.
testing
Use when the user wants to create, query, audit, or initialize an Obsidian vault — saving notes/ideas/URLs into it ("save this" / "file this back" included), querying vault knowledge, auditing health (missing links, orphans, drift), ingesting files, or registering vaults. Not for Excalidraw diagrams — use arc-diagramming-obsidian.
data-ai
Use when specs/<spec-id>/dag.yaml has 2+ ready epics and the lead is staying present to monitor epic-level parallel work via agent teammates. Trigger on mentions of agent teams/teammates for multi-epic work, or after arc-planning yields multiple ready epics. For walk-away unattended execution, use arc-looping.
data-ai
Use when the user wants an Excalidraw diagram or any visual representation — architecture, flowchart, mind map — including casual "draw this" / "show me how this works visually". Also use when arc-maintaining-obsidian delegates Synthesis visuals beyond embedded Mermaid.