jkjamies

Convert acceptance criteria, Jira tickets, Gherkin scenarios, PRDs, or any product requirements into a structured spec template. Use when translating PM artifacts into actionable specs for add-*, update, migrate, or remove skills.

Scaffold a complete new feature module with all 6 submodules, source files, tests, fakes, and AGENTS.md. Use when adding an entirely new feature to the app.

Execute cross-cutting migrations — library swaps, pattern changes, API version upgrades, or architecture refactors. Handles phased rollout, coexistence, and rollback planning.

Reverse-engineer a spec from existing code — reconstructs presumed acceptance criteria, data flow, API contracts, UI states, and business rules by reading source, tests, and git history. Use when inheriting undocumented features, onboarding onto unfamiliar code, or preparing for a refactor.

Modify existing feature code across all affected layers — domain models, data, presentation, tests, and fakes. Use when changing behavior, adding fields, or enhancing existing features.

Verification pipeline with three scopes — diff (default, changed modules only), full (whole project lint + unit + arch + builds), and all (every test level + every variant + full assemble). Use after any code change.

Add, run, and analyze macrobenchmarks — Android Macrobenchmark (Perfetto) and iOS XCTest performance metrics. Scoped to authored, repeatable performance measurements against production-representative builds. Use when startup, scroll, or frame-timing regressions need regression-gated coverage.

Run the full test pipeline (lint + all 5 test levels on both platforms). Mirrors the CI pipeline in verification.md minus the final `./gradlew assemble` step. Device/simulator/emulator required for steps 4+.

Update the okf/ knowledge bundle after a change to the system — the touched concepts, their index entries, the affected diagrams, and the bundle log. Use at the end of any change that alters system shape (an agent, a Kind, a route, a check name, a package, an env var, a port convention), or standalone when the bundle has drifted from reality.

Convert acceptance criteria, Jira tickets, Gherkin scenarios, PRDs, or any product requirements into a filled-in spec under specs/ using this repo's templates. Use when translating PM artifacts or informal asks into an add, change, migrate, or remove spec ready for implementation.

Scaffold a new deterministic, agent-free tooling package on the modern pair, with tests and its knowledge concept. Use when the system needs a new platform capability (an API client, ingress, transport, notifier-style package) rather than a new workflow.

Scaffold a new workflow agent end-to-end on the modern pair — ingest Kind, dispatcher registration, agent package, tests, webhook route, and the knowledge updates. Use when adding an entirely new workflow (a new fixer, digest, or reviewer-style agent) to the system.

Interview the user one question at a time to resolve every unfilled marker in a spec file (`<!-- TODO -->`, raw template placeholder prose, `<YYYY-MM-DD>`-style header stubs, empty plan steps, unconfirmed reverse-spec presumptions). Use on hand-authored specs, stale specs, or when the user says "grill me" or "stress-test this plan". The conversion skills (/ac-to-spec, /reverse-spec) embed this logic inline, so freshly-converted specs don't need a separate pass. Recommends an answer for every question, explores the codebase and okf bundle instead of asking when it can, and writes resolutions back with a Decisions log.

Execute a library, API, or framework swap on a port — mechanical migration that preserves observable behavior, verified against the shipped API. Use when bumping a major SDK version (e.g. the ADK), swapping a library, or moving to a new provider API.

Reverse-engineer a spec from existing code — reconstructs presumed intent, event flow, external contracts, config, and business rules by reading source, tests, prompts, and git history. Use when inheriting undocumented behavior, onboarding onto a workflow agent or platform package, checking modern-pair drift, or capturing a baseline before a change or migration.

The house pre-PR flow — port gates green, CodeRabbit CLI review on the branch diff, evidence-based triage, then present everything and WAIT for human approval. Use when a branch is feature-complete, before any commit/push/PR.

Quick review of the current diff for bugs, logic errors, convention violations, and test gaps

Scaffold a new feature module with the appropriate layers and MESA conventions

Scaffold a new Strata interactor with interface, implementation, fake, and test

Add a new screen to an existing feature module with StateHolder, UI, factories, and tests

Add missing test cases, targeting a specific file or all changed files on the branch

Bump library versions in gradle.properties and prepare release notes

Diagnose and fix an error from a build failure, stack trace, or error message

Thorough pre-merge audit — dependency graph, correctness, conventions, security, test coverage, and improvement suggestions

Add a new screen to an existing feature module with Store, UI, factories, and tests

Add missing test cases, targeting a specific file or all changed files on the branch

Thorough pre-merge audit — dependency graph, correctness, conventions, security, test coverage, and improvement suggestions

Quick review of the current diff for bugs, logic errors, convention violations, and test gaps

Scaffold a new feature module with the appropriate layers and MESA conventions

Scaffold a new Strata interactor with interface, implementation, fake, and test

Bump library version in VERSION file and prepare release notes

Diagnose and fix an error from a build failure, stack trace, or error message

Generate Clean Architecture module structure using the CAMMP MCP server

Generate Clean Architecture module structure for Android/KMP projects (standalone)