22 lines
1.8 KiB
Markdown
22 lines
1.8 KiB
Markdown
# 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](runtime-and-ci.md#execution-context-toolchain-preflight) for exact-context preflight. Before claims, load `development-gates` and `development-integrity`, then [status-and-reporting.md](status-and-reporting.md) and [planning-artifact-reconciliation.md](planning-artifact-reconciliation.md) for project formatting, semantic reconciliation and duplicate suppression.
|
|
|
|
## Common Pitfalls
|
|
|
|
1. Patching symptoms before understanding root cause.
|
|
2. Changing requirements or architecture implicitly through code.
|
|
3. Editing without loading applicable project engineering skills.
|
|
4. Skipping tests for behavioral fixes.
|
|
5. Updating documentation with aspirational rather than actual practice.
|
|
6. Inspecting another project.
|
|
7. Starting implementation because requirements exist but human implementation approval is absent.
|
|
8. Ignoring architecture task dependencies, the Task's `READY_FOR_DELIVERY` handoff, or target-version allocation.
|
|
9. Posting passive status when safe implementation, testing, diagnosis, or documentation work is available.
|
|
10. Treating a human-merged planning or Architecture documentation PR as implementation approval.
|
|
11. Treating an ideation-board entry, generated presentation, or broad approval as equivalent to an exact Task `READY_FOR_DELIVERY` transition—or requiring a second admission after that verified transition.
|
|
12. 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.
|
|
13. 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.
|