liveBook · Manning

Chapter 11: Context engineering for software development

What you will learn in chapter 11 of Context Engineering

Introduces software development as a domain where dependable AI assistance depends on context flowing across the development lifecycle, not just stronger models.

After this chapter you will be able to

What it builds on

Section by section

Introduction

Introduces software development as a domain where dependable AI assistance depends on context flowing across the development lifecycle, not just stronger models.

Key terms: repository state, architectural constraints, test signals, operational metadata, software development lifecycle (SDLC), inline autocomplete, conversational copilots, autonomous coding agents, multi-agent development systems

11.1 AI-assisted coding

Introduces AI-assisted coding as a shift toward directing software development through natural language and context.

Key terms: Software 1.0, Software 2.0, Software 3.0, natural language, context engineering

11.1.1 Stage 0: traditional development

This section defines traditional development as human-led work supported by predefined automation and tools that do not understand code intent.

Key terms: traditional stage, developer, automation, predefined procedures, integrated development environments (IDEs), terminal emulators, basic autocomplete, static analysis, semantic understanding

11.1.2 Stage 1: autocomplete

This section describes the first stage of AI-assisted coding: inline LLM code completion that developers could steer locally but that had little awareness of the wider project.

Key terms: LLM-based code completion, ghost text interface, inline code suggestions, prompt engineering, project architecture, active file

11.1.3 Stage 2: conversational copilots

Stage 2 shifts AI-assisted coding from autocomplete to dialogue while leaving the developer responsible for supplying relevant context.

Key terms: conversational copilots, dialogue, natural language, mostly reactive, relevant code, codebase

11.1.4 Stage 3: AI-native IDEs

This section explains how AI-native IDEs bring repository-aware context and natural-language interaction directly into the development workspace.

Key terms: AI-native IDEs, index the entire repository, RAG, context engineering, natural language prompts, global chat sidebars, inline command bars, @ symbol

11.1.5 Stage 4: coding agents

This section explains how coding agents take on multi-step development tasks and why their work makes context engineering part of the development workflow.

Key terms: coding agent, IDE, CLI-based agents, tools, vibe coding, conversational copilots, intentional context engineering, managed context, repository, tool outputs

11.1.6 Stage 5: agentic systems

Stage 5 extends AI-assisted coding across parallel agent sessions and delegated subagents, making context orchestration and bounded autonomy essential.

Key terms: agent sessions, working context, subagents, delegated subtask, orchestration, route context, partial results, preserve state, boundaries, unrestricted autonomy

11.2 AI-driven software development lifecycle

The section explains how an AI-driven software lifecycle depends on context flowing across stages, and why its faster feedback loops require clear scope, reliable verification, and human review.

Key terms: context continuity, managed context, SDLC, agentic SDLC, feedback loops, rework, intent expression, technical plan, architecture agent, critic agent

11.3 Context engineering applied to software development

Introduces how the following subsections will apply the context engineering stack to software development.

11.3.1 Agent skills for the SDLC

This section explains how agent skills provide repeatable routines across the software development lifecycle and how teams can adopt and verify them.

Key terms: agent skills, SKILL.md, SDLC, quality gates, agent commands, specifications, acceptance criteria, TDD, review, CI/CD

11.3.2 Instruction artifacts in coding agents

This section explains how versioned instruction artifacts give coding agents repository-specific guidance and how shared and tool-specific artifact conventions coexist.

Key terms: instruction artifacts, versioned files, operational context, AGENTS.md, CLAUDE.md, agent-specific instruction artifacts

11.3.3 External knowledge for software development

This section explains why coding agents often use documentation-specific tools for fast-changing external knowledge, while internal RAG remains useful for private corpora.

Key terms: external knowledge, generic RAG pipelines, documentation-specific tools, internal RAG, Context7, Context Hub, chub, local annotations, Exa MCP Server, Ref MCP

11.3.4 MCP servers for the SDLC

Explains how MCP servers let coding agents use engineering tools and data throughout the SDLC, both to gather context and to take action.

Key terms: MCP servers, SDLC, context, engineering environment

11.3.5 Memory for coding agents

This section explains how coding-agent memory should preserve useful project knowledge across sessions and what factors guide a team's choice of memory approach.

Key terms: memory, continuity across sessions, curated project knowledge, long-term memory, tool integration, portability, coding-specific recall

11.3.6 Reusable prompts as context assets

This section explains how reusable, versioned prompt libraries make AI-assisted software development more consistent.

Key terms: reusable prompt library, prompt templates, versioned context assets, specialized SDLC roles, prompting framework, prompting techniques

11.3.7 Specification-driven development

This section explains how specification-driven development makes a specification the central context for AI-assisted software work, distinguishes three levels of use, and recommends adopting them progressively.

Key terms: specification-driven development, SDD, specification, primary context artifact, prompt-first workflow, spec-first, spec-anchored, spec-as-source, source of truth, progressive adoption

11.3.8 Context management for coding agents

This section explains how coding agents keep useful context within token limits and when repository digests are worth using.

Key terms: context management, context window, working set, context editing, compaction, auto memory, pruning, continuation context, repository map, symbols

11.3.9 Context orchestration for coding agents

This section explains how coding-agent orchestration divides software development work among agents with focused contexts and compares ways tools and frameworks put that approach into practice.

Key terms: context orchestration, focused context, SDLC phases, subagents, agent teams, primary agents, context windows, BMAD Method, OpenAgents Control, Open GSD

11.4 Cross-cutting concerns for software development

Explains why software-development agents need cross-cutting safeguards that examine their context, not just their generated code.

Key terms: context sources, context management, context orchestration, evaluation, observability, governance, coding agent, SDLC, context layer, green test suite

11.4.1 Evaluation

This section explains how to evaluate coding agents’ results and processes, use evals to guide development, and interpret coding-agent benchmarks.

Key terms: final artifact, path, context traces, tool-call logs, eval-driven development, EDD, evals, regressions, deterministic metrics, qualitative metrics

11.4.2 Observability

This section explains how teams can trace AI-assisted code changes back to their context and actions, then connect those changes to review, delivery, and production outcomes.

Key terms: observability, causality, context patterns, hidden rework, context traces, tool-call and command logs, active instruction artifacts, cost and latency, review and rework signals, defect and incident correlation

11.4.3 Governance

This section translates governance principles into controls over coding agents’ context, credentials, actions, and accountability.

Key terms: context sources, sensitive data, minimum repository, document, or production data, identity, agent credentials, role-based access control, staged authority, repository-scoped permissions, approval gates, engineering assets

11.4.4 Operations

The section explains how operational routines keep coding agents’ development context and tools current and reliable.

Key terms: context assets, maintained engineering artifacts, version control, removal rules, tool health, development workflow, MCP servers, weaker context

11.5 Hands-on

The section introduces seven implementations of one backlog-scoring feature so readers can compare how context engineering patterns shape development workflows.

Key terms: backlog-scoring feature, toolchain, context pattern

11.5.1 SDD with Spec Kit

Shows how Spec Kit uses a staged, specification-driven workflow and durable artifacts to provide context for a coding agent.

Key terms: Spec Kit, SDD workflow, consistency, specification, plan, task list, durable artifacts, central context asset

11.5.2 Claude Code with agent skills

Shows how Claude Code combines agent skills, local files, and a user prompt to make a coding task a staged SDLC workflow.

Key terms: agent skills, public skill pack, CLAUDE.md, agent-skills-workflow.md, user prompt, executable context assets, staged SDLC workflow, skill commands

11.5.3 Cursor with instructions

Shows how Cursor instruction rules guide a coding agent toward deliberate, minimal, scoped, and verifiable changes.

Key terms: Think before coding, Simplicity first, Surgical changes, Goal-driven execution, custom rule file, .cursor/rules/karpathy-guidelines.mdc, .py glob

11.5.4 Codex with Context7

This hands-on example shows how Codex can combine repository context, current library documentation from Context7, and test feedback while implementing code.

Key terms: Codex, Context7, version-specific documentation, repository context, external technical knowledge, execution feedback, test suite

11.5.5 OpenCode with Superpowers

Shows how Superpowers structures an OpenCode coding workflow around design and planning before source code.

Key terms: Superpowers, superpowers/brainstorming, superpowers/writing-plans, superpowers/test-driven-development, docs/superpowers/specs/, docs/superpowers/plans/, OpenCode, plugin, opencode.json

11.5.6 Antigravity with Open GSD

Shows how Open GSD gives an existing coding agent a staged development workflow and keeps its project state in workspace files.

Key terms: Open GSD, Antigravity, structured workflow layer, .planning/, REQUIREMENTS.md, ROADMAP.md, STATE.md, .planning/phases/

11.5.7 Specialized agents with the BMAD Method

This section shows how the BMAD Method organizes a coding workspace and isolates context by assigning work to specialized agents.

Key terms: _bmad/, _bmad-output/, _bmad/agents/, role decomposition, context isolation, product manager, architect, developer, reviewer

11.5.8 Comparing the hands-on workflows

The section compares hands-on coding workflows by the context artifacts they prioritize and the coordination costs that justify using them.

Key terms: source of truth, specification, skill, rule file, memory store, coordination cost, documentation-grounded agent, spec-driven workflow, multi-agent orchestration, context boundaries

11.6 Summary

Concepts explained in this chapter

← Chapter 10: AI frameworks for context engineering Chapter 12: The state of the art in context engineering →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.