27 lines
2.2 KiB
Markdown
27 lines
2.2 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.
|
|
|
|
## Common Pitfalls
|
|
|
|
1. Patching symptoms before understanding root cause.
|
|
2. Changing requirements or architecture implicitly through code.
|
|
3. Claiming CI success from a local build.
|
|
4. Editing without loading applicable project engineering skills.
|
|
5. Skipping tests for behavioral fixes.
|
|
6. Updating documentation with aspirational rather than actual practice.
|
|
7. Repeatedly posting unchanged failure summaries.
|
|
8. Inspecting another project.
|
|
9. Starting implementation because requirements exist but human implementation approval is absent.
|
|
10. Ignoring architecture task dependencies, the Task's `READY_FOR_DELIVERY` handoff, or target-version allocation.
|
|
11. Posting passive status when safe implementation, testing, diagnosis, or documentation work is available.
|
|
12. Treating a human-merged planning or Architecture documentation PR as implementation approval.
|
|
13. 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.
|
|
14. Validating a stale channel-reported SHA instead of freshly resolving and checking the current remote merge head.
|
|
15. Continuing to report or validate an open PR head after the PR merged during the run; re-resolve the merge/default-branch SHA and require local validation plus CI for that exact merge commit.
|
|
16. Reposting an unchanged gate summary when no new decision, head, CI result, failure, or durable artifact exists.
|
|
17. 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.
|
|
18. Starting `pnpm`, tests, or a background worker before checking the toolchain and required environment inside that exact execution context.
|
|
19. Reporting only “failed” or leading with hashes instead of the linked branch/PR and the exact failed command, file, test, or CI job.
|
|
20. 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.
|