Graph Works

Plugin gw in psprowls/graph-works-codex-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (19)

• archive

  Invoked explicitly as /gw:archive [work-path...]. Archives terminal-status work items (resolved/wontfix/superseded) via `gw work archive` — sweep mode with no arguments, targeted mode with canonical paths — presenting the plan and asking for confirmation before executing. Mutates the workspace; expl

• auto-drive

  Use when driving a work item's full pipeline unattended via Orca-supervised workers — an epic's entire dependency graph or a lone item's phase sequence — instead of walking one /gw:workflow stage at a time by hand. Runs a stateless plan/act/wait coordinator loop over `gw work orchestrate` and the Or

• epic-design

  Use when dispatched as the design stage of an Epic or Release work item that has no spec yet — owns the whole design stage for a decomposition-shaped item, producing the owning item's design plus a thin child index, and never filing children.

• file

  Invoked explicitly as /gw:file. Interactively files a new path-native work item — gathers title, kind, summary, and affects conversationally, estimates effort, then invokes `gw work file` with the assembled values and reports the canonical path. Explicit invocation only, with one exception — the ski

• finishing-relay

  Use when the finish stage of a work item is dispatched under auto-drive with mode relay — sends one orca orchestration ask carrying the merge/PR/hold/discard decision instead of finishing-a-development-branch's interactive menu, executes the chosen outcome, and settles the item. Dispatched by the gw

• graph-works

  Use when building or maintaining a persistent wiki alongside any source-code project — single packages, monorepos, or hybrid shapes. Builds a code graph and renders one page per entity (repository, package, app, agent_plugin, dependency, test_suite) nested under repositories/<repo>/ (one folder per

• ingest

  Use when the user says "ingest this", "add this spec/article/PR to the wiki", or invokes /gw:ingest <path>. Reads a source file from any path, proposes TL;DR and key claims, identifies which code entities and pages will be touched, flags contradictions with wiki or code, proposes ADRs when decisions

• lint

  Use when the user says "lint the wiki" or "check the wiki", weekly, after batch ingests, or after a scan — or when they invoke /gw:lint. Runs mechanical checks (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps, code drift), semantic checks (contradictions vault↔vau

• log

  Invoked explicitly as /gw:log [--last N] [--op scan|ingest|query|lint|...]. Shows recent entries from the workspace log at <workspace>/okf/log.md, which uses the standardized `## [YYYY-MM-DD] <op> | <title>` header format so grep plus tail works. Explicit invocation only.

• onboard

  Invoked explicitly as /gw:onboard. Locates or creates the graph-works workspace, then configures it — one guided walk covering workspace location, topic, the repository it catalogs, and optional session transcript capture. Writes the workspace manifest and repo settings through `gw`; explicit invoca

• planning-epics

  Use when dispatched as the plan stage of an Epic or Release work item.

• proposals

  Invoked explicitly as /gw:proposals [slug...]. Reviews and disposes of curated-page proposals in okf/proposals/ — accept, reject, or supersede. Approving only flips a note's status; this skill then fans out one subagent per accepted proposal to author the destination page, flips notes to created, re

• query

  Use when the user asks a substantive question about the repo that the wiki might answer, or invokes /gw:query "<question>". Reads index.md first, drills into 3-10 relevant pages across categories (concepts, entities, ADRs, sources, work), synthesizes an answer with inline root-absolute markdown link

• reconciling-spec

  Use when a design spec already exists for a work item and the item is entering or re-entering the design stage — updates the spec against whatever has landed since it was written instead of re-brainstorming from scratch, then advances, or holds when the spec and landed code genuinely contradict each

• regen-index

  Invoked explicitly as /gw:regen-index. Reconciles every path-native work-lane index against the filesystem via `gw work regen-index`, then reports the index paths and any warnings or refusals. Run after out-of-band work-item edits. Explicit invocation only.

• scan

  Use when the user says "scan the monorepo", "update entity pages", "catch the wiki up to the code", or invokes /gw:scan. Walks the repo, builds the code graph, and writes one graph-derived page per admitted entity (repository, package, app, agent_plugin, dependency, test_suite) nested under reposito

• status

  Invoked explicitly as /gw:status. Shows a one-screen path-native work item rollup from `gw work status` — totals and counts by work status, type, and phase, plus the canonical path worth resuming and its alternatives. Explicit invocation only.

• using-graph-works

  Use when starting any conversation - establishes how to find and use skills, and how the graph-works work-item pipeline is driven

• workflow

  Use when driving a work item through its development pipeline — runs `gw work next` to compute the stage, dispatches the stage skill (brainstorming, reconciling-spec, epic-design, systematic-debugging, writing-plans, planning-epics, subagent-driven-development, test-driven-development, finishing-a-d

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" skill-doc-routing

Similar plugins