endalk200

Validate and triage pull-request review findings before addressing selected items.

Review changes since a fixed point (commit, branch, tag, or merge-base) along two axes - Standards (does the code follow this repository's documented coding standards?) and Spec (does the code match what the originating issue or PRD asked for?). Runs both reviews in parallel subagents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Create git commits using Conventional Commits. Use when the user asks to commit code, prepare a commit, write a commit message, or standardize commit history with conventional commit types, scopes, breaking-change markers, and safe git workflow checks.

Publish the current branch as a review-ready pull or merge request.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Opinionated guide for building production TypeScript applications with Effect v4. Use when implementing Effect workflows, services, layers, schemas, configuration, schedules, caches, streams, HTTP clients, Effect Atom or API-backed frontend state, or tests.

A relentless interview to sharpen a plan or design.

Validate and triage pull-request review findings before addressing selected items.

A relentless interview to sharpen a plan or design.

Grill the user relentlessly to sharpen a plan or design while maintaining ADRs and domain glossary documentation. Use when the user asks to "grill with docs" or wants decisions documented during a design interview.

Compact the current conversation into a handoff document for another agent to pick up.

Implement a piece of work based on a spec or set of tickets.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Configure this repo for the engineering skills — set up its issue tracker, triage and Wayfinder label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Use Belfry to set up local observability, export OpenTelemetry traces or logs, or debug a Service through bounded searches and exact trace/span/log correlations.

A relentless interview to sharpen a plan or design.

Grill the user relentlessly to sharpen a plan or design while maintaining ADRs and domain glossary documentation. Use when the user asks to "grill with docs" or wants decisions documented during a design interview.

Implement a piece of work based on a spec or set of tickets.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Configure this repo for the engineering skills — set up its issue tracker, triage and Wayfinder label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Use when working with Effect or @effect/platform-node code. Resolve version-matched dependency source with opensrc before relying on memory, docs summaries, or generated examples.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Create git commits using Conventional Commits. Use when the user asks to commit code, prepare a commit, write a commit message, or standardize commit history with conventional commit types, scopes, breaking-change markers, and safe git workflow checks.

Fetch dependency source code so agents can inspect real implementations, tests, and version-specific behavior. Use when docs or types are insufficient, when debugging library internals, or when tasks require source-backed evidence. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", and "opensrc path".

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Break a plan, spec, or PRD into independently-grabbable local markdown issues under `.workflows/` using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tasks, or break down work into issues.

Turn the current conversation context into a local markdown PRD under `.workflows/prd/`. Use when user wants to create a PRD from the current context.

Prepare publishable SDK package changes for push and PR in better-webhook. Use when changes under packages/* need a Changeset, SDK docs or README updates, full verification, and a release-ready PR summary before code is pushed to GitHub.

Required procedure for answering questions about the client - grounding, citation format, conflict handling, and how to say "not in the workspace".

How to record completed work in logs/agent-log.md so humans can inspect what the agent read, wrote, and concluded.

How to create deliverable artifacts (meeting prep briefs, draft emails, analyses) in artifacts/ with required structure and source manifests.

How to extract durable memories from sources and write them as reviewable candidate memory files with provenance, confidence, and sensitivity.

How to orient inside a client workspace - the directory layout, the manifest, provenance records, and which sources outrank which.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Use when working with Effect, @effect/platform-node, ai, or @ai-sdk/devtools code. Resolve version-matched dependency source with opensrc before relying on memory, docs summaries, or generated examples.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

Build a disposable prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Teach the user a new skill or concept, within this workspace.