Skill Claude Code needs its repo
Use when deciding, writing, merging, or updating compact package-driven capability maps under docs/features.
Shared skills, workflows and coding harness configuration to use for projects
This repository also configures its own agents. See what agentic-coding tells them →
Skill Claude Code needs its repo
Use when deciding, writing, merging, or updating compact package-driven capability maps under docs/features.
Skill Claude Code
Use when GitHub PR feedback lives in plain comments, inline comments, issue comments, or review threads.
Skill Claude Code
Use when a design, plan, spec, or business idea must be stress-tested against the authoritative docs the calling workflow's role doc names — sharpens terminology and, when allowed, updates glossaries and decision records inline.
Skill Claude Code
Use when an unclear feature idea needs an approved spec.md — collaborative dialogue that grills the design against the domain model and stops at the approved spec.
Skill Claude Code
Use when an error log, stack trace, or behavior description needs root-cause investigation and a structured GitHub issue — analysis only, no bug fixes.
Skill Claude Code
Use when an implemented, reviewed feature must be finalized — write durable feature documentation when warranted, reconcile glossary/ADRs, and clean up the working plan.
Skill Claude Code
Use when turning an approved spec or clear requirements into a reviewable plan.md with checkbox tasks and TDD steps — resolves every fork during planning and ships zero open questions.
Skill Claude Code
Use when reviewing implemented code changes — report findings first, track feedback in a ledger, and write an approved fix plan under plans/ when needed.
Skill Claude Code
Use when reviewing a spec or plan before implementation — report findings first, track feedback in a ledger, and finalize the reviewed artifacts after approval.
Skill Claude Code
Use when a workflow must publish the current non-protected branch to GitHub, ensure a PR exists, or force-update a retained PR head branch under a lease.
Skill Claude CodeCodex
Use when a business idea must become a correctly labeled issue (or a reasoned rejection) through owner dialogue grounded in the business context docs — stops at the issue.
Skill Claude Code
Use when implementing exactly one approved plan task as a dispatched worker — edit only assigned files, run role-defined verification, and return a structured status report.
Skill Claude Code
Use when executing an approved plan task-by-task — dispatch implement-task workers, own task acceptance, and verify before any completion claim.
Skill Claude Code
Use when writing or validating implementation or review-fix plan artifacts — directory layout, file names, index-to-task links, numbering, and slug rules.
Skill Claude CodeCodex
Use when implementing one self-contained UI-design task packet as a dispatched worker — edit only the packet's owned presentation files and report files and evidence without tests, verification, or commits.
Skill Claude CodeCodex
Use when an approved specification marks ui-design: required — produce approved presentation code through a preview-first interactive loop with ui-design-task workers, inspect every scenario and viewport against the live preview, and write the final handoff.
Skill Claude Code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — run the verification commands and confirm their output before making any success claim.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: