docs: remove deleted project docs skill requirement
This commit is contained in:
1 parent
515b545b32
commit
bb115a3382
13 files changed
+114
-59
No files matched your search
@@ -2,14 +2,15 @@
|
||||
|
||||
Before planning, confirm:
|
||||
|
||||
- I know the task ID, mode, branch, worktree, base commit, and ownership result.
|
||||
- I read the active task record and know its scope.
|
||||
- I know the current branch, absolute worktree, base commit, Git status, and task scope.
|
||||
- For repository-changing work, I read or created the active task record and know its scope.
|
||||
- I know what this project is and what it is not.
|
||||
- I treat current-state as the last integrated snapshot rather than live concurrent state.
|
||||
- I checked active decisions and the architecture overview.
|
||||
- I identified task-specific docs that need deeper reading.
|
||||
- I inspected other local task records through `task_context.py status --json`.
|
||||
- I inspected `git worktree list --porcelain` and any available peer task records relevant to this scope.
|
||||
- I assessed code overlap separately from semantic or decision conflict.
|
||||
- I reported missing peer records as unknown coordination state.
|
||||
- I can name unknown, stale, or conflicting information.
|
||||
- I know which updates remain task-scoped and which require Integration Gate.
|
||||
- I did not rely on an external project-document Skill or task registry.
|
||||
Reference in new issue
Block a user