parsoFish
@parsoFish
Public Skills
tiered-orchestration
by parsoFish
Use when driving a roadmap-scale body of work autonomously across many context windows — several initiatives or lanes, each with its own gates, running unattended between operator rulings — or when one agent's context cannot hold a whole campaign and its reported status keeps drifting from what git and gh say.
reflector
by parsoFish
Run a deep structured retrospective at the end of a merged initiative — repeated actions, roadblocks hit, and operator notes (agentic self-reflection + agent-prompted user questions + pure user feedback) — and write the findings into the central forge-owned brain.
project-manager
by parsoFish
forge's plan agent — decomposes the architect's finalised initiative into atomic, dependency-ordered spec-work-items (ADR-015's versioned artifact contract) for the develop agent's ralph loop to consume.
project-brain-builder
by parsoFish
Read a managed project from scratch and author its initial brain — real theme pages (patterns, conventions, structure) grounded in the project's current state.
preflight-fix
by parsoFish
Apply one operator-approved fix to a managed project to clear a specific forge preflight contract clause.
demo-agent
by parsoFish
"The declaration carrier and display identity for the develop flow's integrate node — the INTEGRATE band (spec §5 item 4). The band is an orchestrator verb: it derives the demo bundle and the PR body from the acceptance criteria, the merge gate's own evidence and the diff, then renders and captures. No model is spawned on any path — see 'What this is, honestly' below."
forge-onboard-project
by parsoFish
Bring any code project up to the forge↔Studio project contract so forge can develop it unattended at roadmap scale. Use before pointing forge at a new or not-yet-primed managed project. Works for any form — UI app, HTTP API, library, CLI, monorepo, infra provider — by authoring the project as a Studio object, mapping each operational contract invariant onto that project's shape, then validating (forge preflight + UI readiness) and handing off a roadmap-scale initiative. The contract spec is docs/reference/project-contract.md (ADR-034).
architect
by parsoFish
Interactive ideation session that turns ideas into a PLAN.md the operator reviews before any manifest is queued.
brain-ingest
by parsoFish
Append raw sources to the brain and create or update theme pages. Never modifies raw in place; never deletes.
immutable-gates
by parsoFish
Make acceptance tests the agent cannot weaken, and prove a test measures what it claims. Use when an agent both writes code and runs the tests that judge it, when pinning acceptance criteria before implementation, or when a test suite is green but trust in it is low.
cruft-sweep
by parsoFish
Rule-based, directory-by-directory cleanup of generated/abandoned/scratch cruft from the forge tree. Every removal is justified by an EXPLICIT rule, never a hardcoded path, so the rule set stays auditable and adjustable. Reports a plan before deleting; deletes nothing matched by a SAFETY exclusion.
journey-sync
by parsoFish
Keep the story suite (tests/stories/) in sync with forge-ui changes. Use whenever a change touches forge-ui load-bearing state (data-* attributes, routes, surfaces, flows/agents/skills/KB affordances), when adding or retiring a Studio capability, or before closing any session that modified forge-ui. The stories are BOTH the demo and the UI regression gate — a UI change without a story update either breaks the gate or silently rots the demo.
live-proof-skill
by parsoFish
Summarise a git diff into three bullet points — what changed, why it matters, and what to test.
security-review
by parsoFish
Use before committing any change that touches authentication, external input, a filesystem or network sink, an API surface, or a spawn/exec path. Derives the review range from this repo's own remote and refuses rather than guessing.
demo-builder
by parsoFish
Author a project's reusable demo-generation skill — the machinery that showcases an initiative's CHANGES (before/after) as a Forge-styled HTML page — and render a real sample from a recent change, iterating on operator feedback until locked.
onboarding-agent
by parsoFish
Bring an existing project up to the forge↔project contract so forge can develop it unattended — declare the quality gate, converge preflight to contract-green, bind the KB, and report what remains.
demo
by parsoFish
The canonical forge demo capability — how forge runs a demo, what every demo must contain, and how the demo maps to the forge UI review page. A demo makes ONE behavioural delta (prior → new) visible, grounded in the initiative's acceptance criteria. The demo phase agent (skills/demo-agent, R4-07) composes this skill to author the structured demo.json and derive DEMO.md. The demo agent reads the project's generated demo skill (from skills/demo-design) to know what evidence to produce; this skill defines the contract that evidence must satisfy. Scale demo effort to the size of the change.
project-scoped-review
by parsoFish
Audit a managed project's actual end state — code, tests, docs, release surface — against the roadmap/initiative intents that were supposed to produce it, hunting drift (promised-but-absent capabilities, orphaned/half-landed work, doc/code contradictions, silent scope cuts).
release-finalizer
by parsoFish
After the operator approves a merged-ready cycle, finalise the release on the PR branch — compute the semver bump, promote the draft changelog entry to a versioned section, run the project's declared pre-merge release steps, optionally bump the version file, then commit and push to the PR branch BEFORE forge merges. Tag/publish stay with CI.
Web Conventions Skill
by parsoFish
against the actually-running server, never the source.
API Conventions Skill
by parsoFish
against the actually-running server, never the source.
CLI Conventions Skill
by parsoFish
source.
demo-design
by parsoFish
Forge-owned generator skill that reads a project's demoProcess + its actual code and generates per-project demo machinery (a repo skill and/or CI step and/or test) committed into the project repo. Run when an operator saves a project's demoProcess in Studio. The generator PRODUCES; the project's own toolchain EXECUTES the generated artifact. Operators customize by editing the generated files (committed repo files) and by editing this generator skill.
adversarial-review
by parsoFish
"forge's ONE review agent — initiative-context critique of the developed diff under the lenses the initiative's CHANGE CLASS declares, plus a verdict on every acceptance criterion and a Why/What/How of the change. Emits a findings artifact with per-finding severity and file:line evidence pointers, weighed by the operator at the verdict gate; it judges, it never edits, it cannot run anything, and the approve/merge decision stays with the operator (ADR 021)."