Skip to content

Knowledge base

Methodologies and Frameworks

Agentic engineering methods redesign how humans and agents divide the work, now that humans no longer write every line. Swapping the coding tool while keeping the sprint-based operating model captures only a fraction of the gain.

Written by

Updated:

Agentic Engineering 5

The industry is renegotiating what replaces story-driven delivery. The current frameworks try to redesign the whole system: manifestos on how humans and agents divide work, the spec-driven toolchain, SDKs for building agents and reference setups to copy from. The method for building an agent follows from what an agent is, a program wrapped around a model. Its working shape is a structured cycle that writes each lesson back, with a named person answering for what ships.

Start here

Further reading

Two write-ups on how teams structure agent-assisted work in practice, both from The Refactoring (refactoring.fm) and worth reading before designing a workflow from scratch: How Engineering Teams use AI (opens in a new tab) (12 March 2025) and Vibe-coding workflows (opens in a new tab) (30 April 2025).

Resources

Methodologies & Manifestos

Spec-Driven Development

  • Agent OS (Builder Methods) (opens in a new tab) - Free system for defining and managing coding standards in AI development, discovering standards from your codebase and injecting them into spec shaping.
  • Allium (opens in a new tab) - Specification language that captures behavioral specs alongside implementation to guide AI code generation and keep intent and behavior aligned.
  • BMAD Method (opens in a new tab) - Breakthrough Method for Agile AI-Driven Development: 12+ AI personas plus structured workflows that walk a team through the SDLC from idea to deployment.
  • CCPM (opens in a new tab) - Project-management skill system for agents that drives spec-driven development and parallel execution via GitHub Issues and Git worktrees.
  • Codervisor Lean Spec (opens in a new tab) - Lightweight, flexible Spec-Driven Development (SDD) for AI-powered development.
  • Conductor (Gemini CLI) (opens in a new tab) - Gemini CLI extension for spec-and-plan workflows with centralized context artifacts and version-control conventions for greenfield and brownfield projects.
  • DESIGN.md (Google Labs) (opens in a new tab) - Format spec for describing visual identity to coding agents, combining YAML design tokens with prose rationale, plus a CLI for linting and WCAG contrast checks.
  • Get Shit Done (GSD) (opens in a new tab) - Lightweight meta-prompting, context-engineering, and spec-driven-development setup for Claude Code by TACHES.
  • GitHub Spec Kit (opens in a new tab) - GitHub’s toolkit for spec-driven development, scaffolding the workflow where written specs steer AI coding assistants.
  • Intent (opens in a new tab) - Contract-based language that compiles a single .intent source to native Rust binaries, JavaScript, and WebAssembly, with pre/postconditions, Z3 SMT verification, and property-based test generation.
  • Kiro (opens in a new tab) - Spec-driven IDE that bridges AI coding and engineering, handling long-running tasks across large codebases with an agent that learns how you work.
  • OpenSpec (opens in a new tab) - Open-source spec-driven development tool by Fission AI for AI coding assistants.
  • RequireKit (opens in a new tab) - AI requirements toolkit using EARS notation for structured specs, BDD/Gherkin generation, epic/feature hierarchy, and optional GuardKit integration.
  • Rezonant (opens in a new tab) - Product workspace that carries product thinking from messy inspiration through to shaped, engineering-ready work for coding agents to build.
  • Spec-Driven Role Prompts (opens in a new tab) - System prompts for a five-role spec-driven workflow with REQUIREMENTS.md to SPEC.md handoffs, traceable requirement IDs, and variants tuned for Claude Code, Codex, and earlier models.
  • Tessl (opens in a new tab) - Spec-driven development tool with a Spec Registry of 10,000+ open-source library specs, giving coding agents structured versioned context.
  • The Website Specification (opens in a new tab) - Platform-agnostic spec of 162 website best practices, the technical things a good website should do, written for humans and agents and queryable via an MCP server and llms.txt.

Agent SDKs & Frameworks

Examples & Templates

In this section

  • The agent loop

    What an agent is made of, how to build one in plain code, and how to debug the step that failed instead of re-running the whole loop.

  • The disciplined compounding loop

    How to run each agent task as plan, test-first build, check and retrospective, and why unstructured generation costs delivery stability.

  • Human accountability

    What stays with the engineer when agents write the code: delegate, review and own, the new middle loop, and three manifestos that put it in writing.

  • Spec-driven development

    How specifications create stable intent and verifiable work for coding agents.