1.8 KiB
1.8 KiB
the adopted project Delivery Pitfalls
Load this reference when a gate fails, when work resumes after interruption, or before reporting a blocker, CI result, merge, or completion.
Before execution, load runtime-and-ci.md for exact-context preflight. Before claims, load development-gates and development-integrity, then status-and-reporting.md and planning-artifact-reconciliation.md for project formatting, semantic reconciliation and duplicate suppression.
Common Pitfalls
- Patching symptoms before understanding root cause.
- Changing requirements or architecture implicitly through code.
- Editing without loading applicable project engineering skills.
- Skipping tests for behavioral fixes.
- Updating documentation with aspirational rather than actual practice.
- Inspecting another project.
- Starting implementation because requirements exist but human implementation approval is absent.
- Ignoring architecture task dependencies, the Task's
READY_FOR_DELIVERYhandoff, or target-version allocation. - Posting passive status when safe implementation, testing, diagnosis, or documentation work is available.
- Treating a human-merged planning or Architecture documentation PR as implementation approval.
- Treating an ideation-board entry, generated presentation, or broad approval as equivalent to an exact Task
READY_FOR_DELIVERYtransition—or requiring a second admission after that verified transition. - Editing in a local-only worktree or on a differently named local branch before the exact remote branch and PR head are visible and verified.
- Stopping at a repairable gate failure, abandoning the active Task, or starting another Task instead of fixing forward and rerunning the gate until it passes.