Based on Oriol Torrent Florensa's usage over the last 30 days (178 sessions):
Work Type Breakdown:
- Improve Quality ████████░░░░░░░░░░░░ 41%
- Build Feature ██████░░░░░░░░░░░░░░ 28%
- Plan & Design ███░░░░░░░░░░░░░░░░░ 13%
- Debug Fix ██░░░░░░░░░░░░░░░░░░ 10%
- Write Docs ██░░░░░░░░░░░░░░░░░░ 8%
Top Skills & Commands:
/grill-with-docs████████████████████ 22x/month/triage██████████████░░░░░░ 15x/month/archon████████████░░░░░░░░ 13x/month/to-tickets████████░░░░░░░░░░░░ 9x/month/tdd██████░░░░░░░░░░░░░░ 7x/month/plugin-dev:skill-development█████░░░░░░░░░░░░░░░ 6x/month/skills█████░░░░░░░░░░░░░░░ 6x/month/archon-rollout████░░░░░░░░░░░░░░░░ 5x/month/to-spec████░░░░░░░░░░░░░░░░ 5x/month
Counts are historical. /to-tickets and /to-spec carry the counts of /to-issues and /to-prd, which upstream renamed at v1.1.
Top MCP Servers:
- Context7 ████████████████████ 4 calls
- unic-agents-plugins — https://github.com/unic/unic-agents-plugins
- Context7 — fetches current docs for libraries, frameworks, SDKs and CLI tools (so answers reflect recent API changes, not stale training data). It ships via the
context7plugin; setCONTEXT7_API_KEY(or runnpx ctx7@latest login) for higher rate limits. - Figma Dev Mode MCP — optional, only needed when using
unic-spec-reviewto review Figma designs; the/unic-spec-review:spec-doctorcommand fails loud if a pasted Figma link needs it and it is not connected. - Playwright MCP — optional, only needed when using
unic-spec-reviewto inspect a live production system; likewise checked by/unic-spec-review:spec-doctor.
- /grill-with-docs — adversarial grilling of a plan against the project's domain model and ADRs, updating CONTEXT.md/ADRs inline as decisions firm up. The team's most-used skill: it stress-tests PR findings and locks designs before any code is written. At upstream v1.1 it thinned to a composition of
/grilling+/domain-modeling, and hands the bigger jobs to/wayfinder. - /wayfinder — the other half of that split, and where upstream moved the planning weight. Charts work too big for one agent session as a
wayfinder:mapissue with child decision tickets, blocked by GitHub's native issue dependencies, and works the frontier one ticket at a time. Reach for it when/grill-with-docswould run out of context. - /triage — moves issues through the 8-state triage workflow; the default for "where do I stand" on open issues and the on-ramp for raw work. It is no longer a gate after
/to-tickets— that approval happens inside the skill. - /archon — runs AI workflows in isolated git worktrees for parallel development; the basis of the team's custom delivery harness.
- /archon-rollout — dispatches
archon-fix-github-issueper issue respecting the dependency tree, with standing guardrails and a deduped monitor; the team's way of shipping a chain of ready-for-agent issues. - /to-tickets — breaks a spec into independently-grabbable issues using tracer-bullet vertical slices. Replaced
/to-issuesat upstream v1.1. - /to-spec — turns the current conversation into a spec and publishes it to the issue tracker. Replaced
/to-prdat upstream v1.1. - /tdd — test-first red-green-refactor loop for building features and fixing bugs.
- /implement — takes a ticket from spec to working code.
- /plugin-dev:skill-development — guidance for authoring and improving Claude Code skills.
- /unic-pr-review:review-pr — multi-agent Azure DevOps PR review (intent checking, Confidence-scored Findings, interactive Approval Loop); the v2 successor to the deprecated
pr-reviewplugin. - /unic-spec-review:review-spec — adversarial eleven-agent review of Confluence web specs (plus Figma and live-system sources), posting selected Findings back as Confluence comments.
- Gitflow, always via PR. Branch from
develop, PR back todevelop;mainonly takes release merges. Usefeature/<name>for all develop-targeting work (features and bugs);hotfix/is reserved for fixes branched offmain. Small doc/housekeeping changes can go straight todevelop. - Run the verification loop before pushing.
pnpm ci:check(not justpnpm format— Biome's import sorting is not auto-fixed byformat), thenpnpm testandpnpm typecheck. CI runs all three OSes × Node 22/24, so check cross-platform assumptions (usenode:path/node:fs, not shell commands). - Versioning is scripted. Bump with
pnpm --filter <plugin> bump <patch|minor|major>— never hand-editmarketplace.json. CHANGELOG headers must be## [X.Y.Z] — YYYY-MM-DD, andverify:changeloggates any PR that touches guarded files (commands, scripts,plugin.json, pluginREADME.md). - Never create or delete
LICENSEfiles — the maintainer manages those by hand in every package. - Spec-first delivery. Work flows
/wayfinder(or/grill-with-docswhen it fits in one session) →/to-spec→/to-tickets→/archon-rollout./to-ticketspublishesready-for-agenttickets only after you approve its breakdown in-session — that approval is the only gate before an agent picks the work up, so read the acceptance criteria there./to-speclabels the spec issue the same way, and that one is not implementable: check an Issue has## What to buildbefore dispatching it. - Trust CI on GitHub, not an agent's self-report. When an Archon run reports "all green / mergeable," confirm with
gh pr checks <n>before merging — the run summary and its exit code can both mislead.
A good first task is getting the workspace green locally:
pnpm installpnpm ci:check && pnpm test && pnpm typecheck— all should pass on a cleandevelop.- Skim
CONTEXT-MAP.mdat the repo root to see the bounded contexts, then read one plugin'sCONTEXT.mdand itsdocs/adr/to learn how decisions are recorded.
From there, run /triage to see where open issues stand, and pick up a ready-for-agent issue or pair on a triage pass.