From Intent to Shipped

Talk through what you want — users, scope, success criteria. Claudia interviews and writes a versioned product.md you can refine over time.

Your call. Judgement: what to build, and for whom

Research the stack, weigh trade-offs, and draft solution.md: system boundaries, data, APIs, auth, infrastructure. You pick the trade-offs that matter.

One adaptive skill routes each need to the right specialist method — research, journeys, web, native mobile, systems, motion, prototypes, or critique — and keeps one living design contract current.

Your call. Taste: the experience you want

Optional acceptance help: contracts, edge cases, and acceptance criteria when ambiguity would make implementation or review unreliable. Skip it when the objective is already buildable.

Capture, connect, deduplicate, and revalidate deferred work on GitHub. You settle outcome, scope, and acceptance, then apply the ready label that admits unattended work.

Your call. Clarity: the ready label

A repository manager carries one coherent objective end to end: reads current evidence, makes the smallest change that satisfies it, opens the draft pull request early, verifies proportionately, and finishes delivery.

Another engineering opinion when you ask for it or when the manager judges it would improve confidence: correctness, regressions, security, compatibility, maintainability. Findings resolved on the head.

Regression, unit, integration, end-to-end, or contract tests for a specific risk or behavior. No test layer is added because the skill was invoked.

Plan, execute, verify, or recover a deployment on the repository’s configured platform. Production authority is confirmed first; database changes keep their own approval.

Your call. Authority: production, unless delegated

Documentation, changelogs, guides, and onboarding drawn from what actually shipped, in the project’s voice, without inventing product behavior.