Further Reading
Read these when a module is the bottleneck. The curriculum is overview first, then deep dive, then references.
Core
docs/curriculum.md— overview map: module, artifact, deep dive, and go-deeper references.docs/intent-engineering.md— clarify intent, burst, pause, structure, iterate.docs/model-fit.md— shape asks around model strengths and supplied context.docs/context-construction.md— construct selective context packs with provenance and stop triggers.docs/prompt-and-context.md— assemble prompt wording, selected context, boundaries, output contract, and checks.docs/open-horizons.md— how the full loop applies to LLM development.docs/problem-space.md— why problem framing needs real terrain.docs/problem-statement.md— narrow terrain into one selected framing.docs/beyond-nearest-peak.md— why cheap generation should change solution search.docs/evidence-and-evals.md— checks before delegation and evals that can fail.docs/agent-briefs.md— turn the selected solution into execution context.docs/authoring-skills.md— write reusableSKILL.mdprocedures.docs/subagents.md— write bounded role agents with scoped tools.docs/execution-review-salvage.md— execute, review, dissent, drift detection, and salvage.docs/knowledge-extraction.md— record metis, signals, guardrails, outcome updates, and ADRs.docs/strategy-clarity.md— aim, mechanism, feedback, guardrails, and solution level.
Strategy background
- Alignment Is the Constraint — aim, mechanism, feedback, and guardrail before speed.
- Documenting Strategy: Lessons from Leading Data and Engineering Teams — vision, stakeholder needs, context, strategy, tactics, and connected work.
- Real-World Application of Strategic Clarity in Platform Leadership — outcomes, mechanisms, updates, feedback, and ownership in a platform team.
LLM mechanics
- LLM Prompt Types — prompt types, suitability, context, and evaluation criteria.
- Anthropic: Effective context engineering for AI agents — context as a finite attention resource.
- Anthropic prompting best practices — clear instructions, context, examples, structure, and grounding.
- OpenAI prompt engineering guide — structured prompts, typed inputs, examples, and evaluation for prompt behavior.
- OpenAI evaluation best practices — eval objective, dataset, metrics, iteration, and continuous evaluation.
- Anthropic: Demystifying evals for AI agents — agent tasks, trials, graders, transcripts, outcomes, and suite maintenance.
- Implementing SLOs for Data Quality — SLI, SLO, error budget, and policy framing for quality.
Later
- Claude Code Skills — official mechanics for
SKILL.md, supporting files, and invocation. - Claude Code Subagents — official mechanics for
.claude/agents/*.md, tool scopes, and role isolation. - Anthropic skill authoring guide — concise skills, progressive disclosure, descriptions, and testing.
- Using GitHub Copilot cloud agent to improve a project — the source shape for mature-project improvement.
- Phoenix Iterative Evaluation & Experimentation Workflow — deeper eval work when regression tests are not enough.
- Open Horizons Skills — the phase skills used by this exercise.
- Intent Engineering — making intent explicit enough that software, agents, and people can use it.
- The Context Stack — why dumping more text into the agent is not the same as giving it the right context.
- Dissent Mode — how to look for flaws before committing.
- The Salvage Loop — when the draft is wrong, keep the learning and drop the draft.
What to read when
If your agent rushes to code, read Intent Engineering and Alignment Is the Constraint. If the model gives fluent but generic output, read Model-Fit Framing, Context Construction, and Prompt and Context Assembly. If problem-space produced a map but not a slice, read Problem Statement. If the agent only proposes one fix, read Beyond the Nearest Peak. If the agent ignores needed context, read The Context Stack. If repeated instructions keep getting pasted, write a skill. If role boundaries keep blurring, write a subagent. If the same lesson keeps being rediscovered, record metis, a signal, a guardrail, an outcome update, or an ADR. If you accept the first plausible implementation, read Dissent Mode. If the run goes sideways, read The Salvage Loop.
Navigation
- Previous: Knowledge Extraction
- Up: Docs Home / Curriculum
- Next: README