Project Context
Purpose
Keep durable repo context in ordinary files so later sessions can resume without rebuilding state.
Use this skill for resume, handoff, long-running work, subagent follow-through, reusable reference context, or task logs. Do not bootstrap it for a read-only question or one-shot inspection. If a repo has existing context docs but no project-context layout, choose explicit adoption or use project-context-migration before creating a parallel tree.
Contract
docs/
reference/**/*.md
tasks/yyyy/mm-dd/<task-slug>/
BRIEF.md
logs/{DECISIONS,WORKLOG}.md
[optional] <purpose-named-backlog>.md
[optional] working/
[optional] archive/
[optional] BACKLOG.md
docs/reference/** owns reusable current rules and reliable facts. Keep investigation history, progress, timelines, code inventories, and provenance narrative out. Point to authoritative code, API, config, test, or project documents instead of restating them. Apply corrections or deletion requests by rewriting or removing stale claims.BRIEF.md is a rewrite-only resume card: stable goal, scope boundary, current conclusions and state, and the nearest restartable step. It is not a report, history, evidence log, file inventory, or backlog. At a phase boundary, rewrite it to the new resume state and move prior evidence or chronology to logs, working/, or archive/.logs/WORKLOG.md records one concise outcome entry per meaningful settled batch, not commands or micro-iterations. logs/DECISIONS.md records only decisions that change future interpretation, scope, architecture, rollback, or rule application. Keep DECISIONS.md empty until there is a decision to record. Let the bundled log helper own exact block shape.- A task root contains current-canonical documents and routers. Keep durable human-readable drafts, investigation notes, undecided plans, methods, and compact evidence summaries in
working/. Put completed, rejected, replaced, or stale context in archive/.
- Keep disposable experiment and browser-test code, state, and raw output in an isolated workspace outside the repository, then discard them after inspection. Put retained code and evidence under their normal repository owner.
- Use a purpose-named task backlog only when one nearest step is insufficient. Keep inactive repo-level work in
docs/BACKLOG.md.
Task Identity and Shared Ownership
- Reuse a task only when the unresolved work and expected output still match. Topic similarity or an old boundary note is not task identity; when uncertain, create a new dated task.
- When multiple tasks, owners, or phases depend on an interpretation that changes implementation or acceptance, assign one current canonical owner. Prefer an existing code, API, config, test, or project-document owner. Otherwise use a purpose-named task-root contract for task-specific meaning or
docs/reference/** for reusable meaning.
- Consumers point to that owner and keep only task-specific state, deviations, and next action. Do not mirror the same open work across brief, backlog, working notes, and logs.
Operation and Validation
Before acting, reconcile the brief's goal, current state, and restart point. When the current state proves the goal complete, close the selected task and keep adjacent next steps as candidates until the user or an authoritative approved plan selects them.
Read the brief first and only the reference or log context needed to act. Reuse the matching unfinished task or create a dated task with the core files; skip creating a new task only for a small, low-judgment change finished immediately. Add optional surfaces only for a distinct owner or reader action.
Assign one writer for the brief and canonical logs. Other agents write them only under an explicit bounded assignment. Use repo-relative paths or stable placeholders, store no secrets, and pass delegated work only the current goal, constraints, unknowns, evidence command, artifact path, and canonical pointers it needs.
Proceed with reversible stated assumptions when context is missing; ask before changing authority or making a hard-to-reverse commitment.
Use the bundled log helper and runtime-shape checker; their scripts own exact mechanics. For routine completion or handoff, run the skill-relative scripts/check_runtime_shape.py --task-root docs/tasks/yyyy/mm-dd/<task-slug>; the task path is relative to the detected repo or explicit --repo-root. Omit --task-root for a repository-wide audit or migration check. The checker covers required shape, latest log blocks, portable paths, and secret-like markers, not ownership, semantic quality, full history, or migration correctness. When a task is maintained, finish only when its brief can reopen the work and current context has one clear owner.
1---2name: project-context-23description: Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.4---56# Project Context78## Purpose910Keep durable repo context in ordinary files so later sessions can resume without rebuilding state.1112Use this skill for resume, handoff, long-running work, subagent follow-through, reusable reference context, or task logs. Do not bootstrap it for a read-only question or one-shot inspection. If a repo has existing context docs but no project-context layout, choose explicit adoption or use `project-context-migration` before creating a parallel tree.1314## Contract1516```text17docs/18 reference/**/*.md19 tasks/yyyy/mm-dd/<task-slug>/20 BRIEF.md21 logs/{DECISIONS,WORKLOG}.md22 [optional] <purpose-named-backlog>.md23 [optional] working/24 [optional] archive/25 [optional] BACKLOG.md26```2728- `docs/reference/**` owns reusable current rules and reliable facts. Keep investigation history, progress, timelines, code inventories, and provenance narrative out. Point to authoritative code, API, config, test, or project documents instead of restating them. Apply corrections or deletion requests by rewriting or removing stale claims.29- `BRIEF.md` is a rewrite-only resume card: stable goal, scope boundary, current conclusions and state, and the nearest restartable step. It is not a report, history, evidence log, file inventory, or backlog. At a phase boundary, rewrite it to the new resume state and move prior evidence or chronology to logs, `working/`, or `archive/`.30- `logs/WORKLOG.md` records one concise outcome entry per meaningful settled batch, not commands or micro-iterations. `logs/DECISIONS.md` records only decisions that change future interpretation, scope, architecture, rollback, or rule application. Keep `DECISIONS.md` empty until there is a decision to record. Let the bundled log helper own exact block shape.31- A task root contains current-canonical documents and routers. Keep durable human-readable drafts, investigation notes, undecided plans, methods, and compact evidence summaries in `working/`. Put completed, rejected, replaced, or stale context in `archive/`.32- Keep disposable experiment and browser-test code, state, and raw output in an isolated workspace outside the repository, then discard them after inspection. Put retained code and evidence under their normal repository owner.33- Use a purpose-named task backlog only when one nearest step is insufficient. Keep inactive repo-level work in `docs/BACKLOG.md`.3435## Task Identity and Shared Ownership3637- Reuse a task only when the unresolved work and expected output still match. Topic similarity or an old boundary note is not task identity; when uncertain, create a new dated task.38- When multiple tasks, owners, or phases depend on an interpretation that changes implementation or acceptance, assign one current canonical owner. Prefer an existing code, API, config, test, or project-document owner. Otherwise use a purpose-named task-root contract for task-specific meaning or `docs/reference/**` for reusable meaning.39- Consumers point to that owner and keep only task-specific state, deviations, and next action. Do not mirror the same open work across brief, backlog, working notes, and logs.4041## Operation and Validation4243Before acting, reconcile the brief's goal, current state, and restart point. When the current state proves the goal complete, close the selected task and keep adjacent next steps as candidates until the user or an authoritative approved plan selects them.4445Read the brief first and only the reference or log context needed to act. Reuse the matching unfinished task or create a dated task with the core files; skip creating a new task only for a small, low-judgment change finished immediately. Add optional surfaces only for a distinct owner or reader action.4647Assign one writer for the brief and canonical logs. Other agents write them only under an explicit bounded assignment. Use repo-relative paths or stable placeholders, store no secrets, and pass delegated work only the current goal, constraints, unknowns, evidence command, artifact path, and canonical pointers it needs.4849Proceed with reversible stated assumptions when context is missing; ask before changing authority or making a hard-to-reverse commitment.5051Use the bundled log helper and runtime-shape checker; their scripts own exact mechanics. For routine completion or handoff, run the skill-relative `scripts/check_runtime_shape.py --task-root docs/tasks/yyyy/mm-dd/<task-slug>`; the task path is relative to the detected repo or explicit `--repo-root`. Omit `--task-root` for a repository-wide audit or migration check. The checker covers required shape, latest log blocks, portable paths, and secret-like markers, not ownership, semantic quality, full history, or migration correctness. When a task is maintained, finish only when its brief can reopen the work and current context has one clear owner.
perhapsspy