Tactical Agentic Coding

Appearance

Tactical Agentic CodingThe field manual

The 8 tactics of Tactical Agentic Coding and the 6 lessons of the Agentic Handbook, distilled into standard operating procedures. Stop coding. Build the system that builds the system.

Start with Tactic 1
The 8 Tactics
Frameworks & Glossary
🛑

Phase Two Engineering

AI coding was phase one. Agentic coding is phase two, where you turn your codebase into a self-operating machine. The mission: become an engineer they cannot replace.

🎯

The Core Four

Context, Model, Prompt, Tools. Every framework in both courses reduces back to these four. Master the primitives and you master the compositions.

📐

12 Leverage Points

Four in-agent levers (the Core Four) and eight through-agent levers: standard out, types, docs, tests, architecture, plans, templates, and ADWs.

📊

The 4 KPIs

Size up. Attempts down. Streak up. Presence down. If you do not measure it, you cannot improve it.

🤖

AFK Agents (PETER)

Prompt input, Trigger, Environment, Review. Write the prompt, kick off the pipeline, go away from keyboard. Prompt to PR.

🔁

Close the Loops

Request, Validate, Resolve. Give agents validators so they self-correct until the job is done. Tests are the rule of law.

🧠

Elite Context Engineering

The R&D framework: Reduce context into the primary agent, Delegate context to sub-agents. A focused agent is a performant agent.

🎛️

The Orchestrator

The one agent to rule them all. It commands primary agents, CRUDs them at scale, and observes everything. Agents that conduct agents.

🌌

Codebase Singularity

The moment your agents ship better than you and your team. Reached by building a sufficiently powerful agentic layer around your codebase.

What this is ​

This is a working reference for two IndyDevDan courses, Tactical Agentic Coding (TAC) and the Agentic Handbook (AH), rebuilt as an SOP site. Each lesson is distilled into an overview, the named frameworks, step-by-step application, the exact commands and directory conventions, key takeaways, and the quotes worth remembering.

The through-line of all fourteen lessons: engineering was never about typing code. It is about building systems of leverage that produce valuable outcomes. Phase one was AI coding. Phase two is agentic coding, where you stop coding by hand and start building the agentic layer that runs your codebase for you.

The two courses ​

Tactical Agentic Coding, the 8 tactics ​

Each lesson centers on exactly one tactic, stacked on top of the last.

  1. Stop coding — your hands are no longer the best tool for writing code.
  2. Adopt your agent's perspective — the 12 Leverage Points and the 4 KPIs.
  3. Template your engineering — meta prompts, higher order prompts, and plans.
  4. Stay out the loop — AFK agents and the PETER framework.
  5. Always add feedback loops — closed-loop prompts: request, validate, resolve.
  6. One agent, one prompt, one purpose — focused agents beat god agents.
  7. Target Zero Touch Engineering — the North Star, where you stop reviewing too.
  8. Prioritize agentics — the meta-tactic: agentic layer over application layer.

The Agentic Handbook, the 6 lessons ​

The deeper track: context, prompts, and multi-agent systems, mostly built on the Claude Agent SDK.

  1. Elite Context Engineering — the R&D framework and 12 context techniques.
  2. Agentic Prompt Engineering — the Stakeholder Trifecta and the Seven Levels of prompt formats.
  3. Building Domain-Specific Agents — better, then more, then custom agents.
  4. The Orchestrator Agent — one interface commanding a fleet of primary agents.
  5. Agent Experts — self-improving agents that learn and reuse expertise.
  6. Codebase Singularity — the classes-and-grades maturity model, and the capstone.

Ask the course

Use the chat button in the bottom-right corner to ask questions across every lesson. It answers from the full course content and cites the lesson it drew from.