gormes-agent

Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.

Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.

Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.

Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.

Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.

Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.

Plan or implement browser automation parity. Use for Browser Use, go-browser-harness, CDP, /browser connect, browser providers, tool descriptors, and browser interaction skills.

Use when the user invokes gormes-git to commit every current Gormes worktree change in coherent split commits, make development green, and push only the existing development branch.

Check Gormes vs Hermes/Honcho parity. Use for behavior sweeps, stale upstream evidence, taxonomy changes, user-visible drift, and source-backed progress-row handoffs.

Map missing Hermes-in-Go parity. Use for upstream Hermes/Honcho feature audits, Goncho compatibility gaps, and source-backed progress-row evidence before builder work.

Turn broad Gormes plans, PRDs, parity gaps, review findings, or user objectives into thin, verifiable progress-row slices.

Use when the user asks to release Gormes, bump the operator-facing version, create a GitHub release tag, publish artifacts, recover a release, or run the full development-to-main release lane.

Audit live ~/.gormes session state. Use for sessions.db locks, memory.db transcripts, gateway state, profiles, permissions, logs, session duplication, and repair planning.

Use when designing, critiquing, or polishing dashboard screenshots, hero images, social cards, visual mockups, or image-based dashboard UI assets for agent/operator products.

Use when Gormes work needs external library, framework, upstream repo, provider API, or reference-project context before planning or implementation.

Run bounded architecture → planner → Hermes parity → builder/TDD cycles. Use when asked for the Gormes delivery loop or to repeat that skill chain with validation controls.

Use when running, installing, rebuilding, or validating local Gormes binaries, go run ./cmd/gormes, bin/gormes, install.sh, managed source clones, PATH shadowing, gateway stop/status, or sessions.db lock issues.

Use when working on Gormes with a persistent long-running objective, a development-goal runner iteration, /goal, gormes goal, keep going, finish Gormes, prove it works, or goal status, pause, resume, clear, or completion requests.

Use when a Gormes pull request has Greptile review feedback or a sub-5/5 Greptile confidence score and the user wants an autonomous fix-review loop until 5/5 or a documented blocker.

Verify Gormes install/setup paths. Use for install.sh/install.ps1, local checkout installs, live binary refresh, install regressions, and fresh-user gormes command proof.

Design Gormes package/API boundaries. Use for provider, gateway, tool, session, memory, Goncho, plugin, API, or TUI seams, unclear write_scope, or design comparison.

Use when the user asks to audit, redesign, polish, rewrite, or periodically improve the www.gormes.ai landing page, homepage UI, visual hierarchy, install flow, public trust signals, or conversion copy from current Gormes evidence.

Discover useful OpenClaw-only behavior absent from Hermes. Use when classifying owned enhancements, adoption risk, or source-backed progress tasks.

Learn reusable Pi harness ideas for Gormes without making Pi a parity target. Use for extensions, tools, SDK/RPC, TUI, sessions, prompts, packages, and provider hooks.

Use when checking a Gormes pull request for unresolved comments, failing checks, incomplete description, missing validation evidence, or merge readiness before Greptile/release review.

Use when exploring a Gormes UI, TUI, protocol, state-machine, or runtime design with throwaway code before committing to production implementation.

Use when fixing or implementing Gormes provider, auth, credential, endpoint, model-routing, streaming, account-usage, rate-limit, retry, or Telegram-visible provider error behavior.

Use when the user asks to audit, score, refresh, fact-check, or periodically improve the Gormes README, public repository messaging, usage docs, install docs, status claims, positioning, or repository-quality evidence.

Find Go donor/reference implementations for Gormes. Use when stuck on implementation shape, checking donor provenance, or comparing Go agent donors.

Use when Gormes work has PR feedback, CI failures, reviewer comments, static-analysis findings, or a need to iterate until a bounded validation target is green.

Use when Greptile is unavailable or before requesting external review to assign a conservative 1-5 production-readiness score to a Gormes change from source evidence and validation results.

Use when a Gormes change creates or reveals duplicated runtime mechanics, repeated channel/provider/setup logic, or feature code that should be reusable before more work builds on it.

Plan or review Flutter Navivox Telegram-like UI. Use for chat thread chrome, bubbles, composer, contacts, action sheets, voice affordances, or Telegram clone references.