gregoryho
33 verified skills142 total stars
arc-verifying
Use when you need to verify work is complete before making completion claims
testing6
arc-writing-tasks
Use when breaking down features into executable tasks, when preparing for implementation, or when tasks need exact code and commands
development6
arc-maintaining-obsidian
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.
testing6
arc-executing-tasks
Use when executing a prepared task list, when running batch implementation, or when tasks are already broken down
tools6
arc-using-worktrees
Use when setting up an isolated workspace for a single epic from dag.yaml, or when a task means scoping work to one epic — even if the user never says "worktree". For batch multi-epic expansion, use arc-coordinating expand.
data-ai6
arc-recalling
Use when the user wants to manually save a pattern or insight as an instinct from the current session context, invokes /arcforge:arc-recalling with a description, or identifies a reusable technique worth preserving
tools6
arc-dispatching-teammates
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-ai6
arc-learning
Use when optional learning is enabled and observations should become reviewable candidates, inactive drafts, and explicitly activated artifacts.
testing6
arc-writing-skills
Use when maintaining ArcForge itself by creating, editing, or verifying ArcForge skills before deployment
testing6
arc-planning
Use when breaking down a structured spec into an executable DAG, when a spec has been refined and epics need to be defined, or when planning feature and epic structure for implementation
tools6
arc-compacting
Guide for strategic manual compaction timing at workflow phase boundaries
documentation6
arc-brainstorming
Use when exploring ideas before implementation or when user wants to design a new feature or iterate on an existing spec
data-ai6
arc-refining
Use when converting design documents to structured specs, when spec quality is below threshold, or when requirements need formal acceptance criteria
testing6
arc-evaluating
Use when measuring whether skills, agents, or workflows actually change AI agent behavior — before shipping a new skill, after modifying an existing one, or when comparing alternative approaches
data-ai6
arc-journaling
Use when the user asks to journal session reflections (/arcforge:arc-journaling), when the PreCompact hook triggers, or at end of a significant work session
tools6
arc-finishing-epic
Use when epic implementation in a worktree is complete (.arcforge-epic file exists), all tests pass, and you need to decide how to integrate
testing6
arc-using
Use when an ArcForge task needs routing help or the user asks which ArcForge skill/workflow applies
tools6
arc-managing-sessions
Use when ending a session and handing off to a future session, summarizing recent context, continuing from where the last turn left off, archiving a session for durable reference, or resuming/listing/aliasing saved sessions
tools6
arc-auditing-spec
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.
testing6
arc-diagramming-obsidian
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.
data-ai6
arc-reflecting
Use when the user asks to reflect on accumulated diaries (/arcforge:arc-reflecting), after 5+ diary entries accumulate, or when asked to summarize preferences from past sessions
tools6
arc-observing
Use when user asks about behavioral patterns, requests instinct status, or wants to confirm/contradict a detected pattern
tools6
arc-implementing
Use when orchestrating large project implementation in a worktree
tools2
arc-researching
Use when optimizing any measurable metric through autonomous hypothesis-driven experimentation — build times, algorithm efficiency, prompt quality, model performance, or any target with a numeric signal
development2
arc-coordinating
Use when managing worktrees for multi-epic projects, when specs/<spec-id>/dag.yaml exists, or when coordinating parallel development
development2
arc-dispatching-parallel
Use when dispatching multiple independent features within a worktree session
tools2
arc-looping
Use when running autonomous unattended loops — cross-session execution of DAG tasks without human intervention
tools2
arc-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development
arc-tdd
Use when implementing any feature or bugfix, before writing implementation code
development
arc-finishing
Use when implementation is complete on a regular branch (no .arcforge-epic file), all tests pass, and you need to decide how to integrate
testing
arc-requesting-review
Use when completing tasks or features to request code review
development
arc-receiving-review
Use when receiving code review feedback, requires technical rigor not performative agreement
development
arc-agent-driven
Use when executing task lists where each task requires isolated execution
data-ai