AthenodeAthenode

Engineering Discipline

A disciplined everyday engineering loop for a coding agent: stress-test the plan, write it down, build it test-first, diagnose bugs with a reproducing signal, and review the diff before it is called done.

Built on Matt Pocock's skills (https://github.com/mattpocock/skills, MIT), imported unmodified, plus the Context7 MCP server for current library documentation.

Start by running /setup-matt-pocock-skills once per repository (it records your issue tracker and doc layout). Then: /grill-me to sharpen a plan, /to-spec to publish it to the issue tracker, /implement to build it with tdd and finish with code-review; diagnosing-bugs for anything broken or slow, codebase-design for module boundaries, research to gather facts in the background.

Prerequisites: none for the skills; the issue-tracker steps use whatever tracker CLI the setup step configures (for GitHub, gh). Context7 works without a key, with lower rate limits.

Not affiliated with Matt Pocock. to-spec writes to your issue tracker, not to Athenode specifications. In Claude Code the code-review skill shares its name with a built-in command.

AGENTS.md

Instructions every agent follows
Engineering discipline
  • Before non-trivial work, state the plan and the open decisions; when a decision is the user's to make, ask instead of assuming.
  • Change behaviour test-first when the project has tests: a failing test that shows the gap, then the smallest change that makes it pass. Say so plainly when you skipped this and why.
  • Fix a bug only after you can reproduce it with a command that fails; keep that command or test as the proof of the fix.

Agents

0
  • Nothing here yet

MCP servers

1
  • context7

Ready to ship better, together?

Spec it. Decompose it. Ship it. All with your AI agent.

Start for free

Join engineers building with Athenode today.