mertefesensoy
UserAn agent company you govern as its architect — a desktop harness that turns the terminal coding CLIs you already pay for into a self-coordinating crew with memory, mailboxes and desks on a 2D floor. Pre-alpha, building in public.
Categories
Indexed Skills (6)
goal
Drive the current milestone's goal run end-to-end — resolve the milestone from docs/PROGRESS.md (M3 as of this writing), enforce the Architect's sole git authorship and a properly named feature branch before any commit, then loop the /build-package cycle through the milestone's packages and close with /milestone-review. Use when asked to run the milestone, start "the M<x> run", or invoked as /goal.
improve
File a Gymnasium self-improvement proposal for Ephesus — scan the repo and its records for the highest-leverage improvement, write a structured proposal with measurable success criteria, and queue it for the Architect. Use when asked to find improvements, when a retro/review surfaces recurring friction, or on a scheduled improvement pass.
research
Run one Stoa research cycle for Ephesus — study ONE Architect-registered repository from docs/stoa/WATCHLIST.md at a pinned commit, scoped by its tags, and file a provenance-cited research brief whose candidates feed /improve. Use when asked to research a watched source, study how another harness solves something, or on a scheduled research pass.
build-package
Execute the next Ephesus work package from BUILD-PROMPT.md — resume from docs/PROGRESS.md, run the READ→PLAN→BUILD→TEST→PROVE→COMMIT→REPORT loop, and never proceed on red checks. Use when asked to continue building Ephesus, implement a milestone/package, or "keep going".
doc-sync
Detect and fix drift between the Ephesus documentation suite and the code — module map vs src/, IPC contract vs handlers, schemas vs validators, invariants vs implementation. Use after landing a milestone, before releases, or when asked whether the docs still tell the truth.
milestone-review
Verify an Ephesus milestone's exit criteria before declaring it done — run the named scenario suites, check every package's evidence, update PROGRESS.md, and produce an architect-facing review. Use when a milestone looks complete or the user asks "are we done with M<x>?".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.