home-v1-skills-code-agent/corp-v1-channel-delivery
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify development skill precedence

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-23 19:45:36 +00:00
parent 6190262538
commit d185f9b2d6
3 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
references/failure-and-documentation.md
+1 -1
View File
@@ -51,7 +51,7 @@ Update these pages from verified project practice. Do not document a planned pro
## Synchronization Workflow
When planning documentation, Architecture structure, or Kanban state changes while implementation remains gated, follow [`references/planning-artifact-reconciliation.md`](references/planning-artifact-reconciliation.md). It defines fresh remote-head discovery, exact-merge-SHA validation, `READY_FOR_DELIVERY` handoff interpretation, evidence boundaries, and duplicate-status suppression.
When planning documentation, Architecture structure, or Kanban state changes while implementation remains gated, follow [`planning-artifact-reconciliation.md`](planning-artifact-reconciliation.md). It defines fresh remote-head discovery, exact-merge-SHA validation, `READY_FOR_DELIVERY` handoff interpretation, evidence boundaries, and duplicate-status suppression.
1. Read new same-project activity and enough delivery history to avoid duplicates.
2. Before claiming new task work, verify exact-item `Approved for Implementation` evidence, exact Task `READY_FOR_DELIVERY` state, task dependencies, approved UI/UX handoff when applicable, and target version.