task-author-review

Auditing task documentation against a codebase requires comparing task pack files like plan.md and work-breakdown.md with actual repository contracts. This review enforces a code-as-truth approach, identifying stale assumptions and misaligned implementations before execution.

Task pack implementation drifts from documented contracts when plans, findings, and work-breakdown files are not updated to reflect codebase changes. Code-first auditing exposes these gaps, stale assumptions, and missing rollout steps to ensure documentation alignment.

Reviewing a task folder for missing rollout steps involves auditing task pack files against real codebase contracts. This process identifies gaps, contract risks, and stale assumptions, providing actionable edits to tighten documentation alignment and safer progress.

Yes, tightening task pack files directly in place aligns plan.md, findings.md, and companion prompts with the current codebase. This code-first audit provides actionable edits and validation guidance to improve accuracy, safety, and ownership before implementation.

Code-first review for task packs is an auditing approach that treats the repository as the source of truth. It validates documented contracts against the implementation, enforcing explicit ownership and validation expectations to guide actionable edits for documentation alignment.

Task pack auditing supports weaker agents by providing actionable edits and validation guidance after tightening plans against the codebase. This ensures safer progress and clearer ownership, giving weaker agents a reliable path toward implementation accuracy.