writing-for-agents

Test-driven development: red before green, one vertical slice at a time.

Deep modules: shared vocabulary for module interfaces and seams.

Read and write the memory vault at ~/.aleph/vault.

Writes and audits technical docs with Diataxis type gating and runnable examples.

Domain model: change a project's glossary and decisions.

Grill the user about a plan, decision or idea until you reach shared understanding.

Save a session handoff so a fresh context can resume the work.

Spec: turn the decisions already made in this conversation into a development spec file, typically after /aleph:grill-me.

Blog posts and essays, including posts that mix technical and non-technical content.

Prior art: survey the open-source projects that solve the same problem as a repo you own, and rank what to take or skip.

Red-team a plan, proposal, design doc or PR description: parallel subagents check it against the code and return a ranked list of flaws.

Tidy a repo: sweep the junk, prove dead code and delete it behind a green build, and gate it as ready to show.