{"id":"outlinedriven-outline-driven-development","name":"outline-driven-development","af_score":31.2,"security_score":19.5,"reliability_score":20.0,"what_it_does":"A workflow/prompt-and-tooling approach for augmented LLM code-agent development that emphasizes an “outline” as the canonical contract (stored with hashes) and revalidation of generated changes against that outline, using AST-based tooling and optional MCP extensions/plugins for agent orchestration.","best_when":"You want repeatable, outline-constrained agent workflows for code editing where AST-based validation and explicit quality gates are important.","avoid_when":"You need a simple “drop-in” SaaS with documented rate limits, SDKs, and standardized auth for a stable API surface; or you cannot install/run the local tooling dependencies.","last_evaluated":"2026-03-30T15:24:43.847471+00:00","has_mcp":false,"has_api":false,"auth_methods":["Provider-specific plugin installation flows (e.g., Claude Code plugin marketplace, Gemini CLI extensions install, local Codex plugin copy). Exact runtime auth for APIs is not described in the provided README."],"has_free_tier":false,"known_gotchas":["Heavily dependency-driven workflow: missing any of the listed CLI tools or MCP extensions may break parts of the intended pipeline.","The approach relies on outline revalidation; if the outline sliceing/versioning strategy is not enforced by your implementation, the determinism benefit may not materialize.","No explicit guidance in the provided README about handling partial failures, retries, or transactional updates to repo state."],"error_quality":0.0}