Back to directory

coding-agent-toolkit

A cross-agent workflow toolkit of seven steps for taking work from idea to merged PR, usable as Claude Code skills or Codex prompts, with shared on-disk state so either agent can pick up a task.

coding-agent-toolkit

coding-agent-toolkit is a set of seven workflow steps, invoked as slash commands in Claude Code or as prompts in Codex, that structure the work around building a feature rather than the coding itself: defining what done means, breaking work into chunks, projecting a plan onto GitHub for review, and carrying context across sessions and hosts.

The align step surveys the codebase read-only and interrogates the user into a spec file; plan breaks the spec into dependency-ordered chunks; plan-issues turns those chunks into a GitHub milestone and issues, dry-run by default; next-issue takes the lowest-numbered open issue in the milestone through implementation, tests and a pull request; and ship closes the milestone. handoff and continue write and replay a snapshot of read-only checks so work can resume after a context limit, restart, or day boundary. Every step ships as both a Claude Code skill and a Codex prompt reading and writing shared state under a workspace directory, so either agent can continue where the other left off.

It is written in Shell and MIT licensed.

More in Agent skills

See all 581
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • A markdown framework of system rules that restates Isaac Asimov's Four Laws of Robotics as a set of prioritized loss calculations for large-language-model agents to follow, published as a discovery file for agents and crawlers to read.

  • Vitruvius

    github.com

    An engineering research agent that runs a discover, read, synthesize, verify and review loop over technical questions, reading sources directly rather than inferring from titles, and publishing its own scored verifier benchmark, weaknesses included.