Local work

Use local files as a lightweight execution queue. Keep the repository spec as the only behavior authority; local work documents control scope, order, progress, and concise evidence without becoming requirements.

Authority and selection

• Accept one current repository-authoritative spec whose exact status means approved for implementation under the consuming repository contract and whose material open questions block no referenced requirement, item boundary, seam, or acceptance criterion. Under the bundled to-spec vocabulary, require 상태: 승인됨; 초안 and 미해결 질문으로 차단됨 are not executable. If approval or open-question impact is absent or ambiguous, create nothing and return status=planning-blocked, the exact missing approval or decision, mutations=none, and resume_condition=approved-authoritative-spec-read. On resume, accept a local-work entry point only to resolve and revalidate that source. Reject an explainer, another non-normative projection, a conversation-only artifact, or an unresolved source identity as the behavior source. If derived_from resolves exactly once, restart from that spec; otherwise create nothing and return status=non-normative-source, the candidate and source identities, mutations=none, and resume_condition=authoritative-repository-spec-read.
• Bind the work set to the exact complete spec-file fingerprint. If that file changes, mark the work set stale and stop before further code edits; regenerate or explicitly reconcile it from the new spec.
• Use documenting-work for the work-set identity, fallback path, index, and lifecycle. Under its fallback, use docs/local-work/<spec-name>/work.md and items/WNNN-<slug>.md.
• Treat work.md as an index and each item as a non-normative execution projection. Items may name source requirement and acceptance IDs, writable scope, order, and verification seam, but must not invent or restate product behavior as a new authority.
• Use tdd for each already-defined behavior change, diagnosing-bugs before fixing an unexplained failure, codebase-design for an unresolved material seam, and code-review for the final pinned change. Return requirement or domain uncertainty to to-spec or decision-map.
• If implementation is already issue-backed or its evidence must update a tracker, create nothing and return status=issue-backed-route, the issue/spec identity, mutations=none, next_workflow=work-github-issue, and resume_condition=issue-readiness-revalidated; do not create a second local execution lifecycle even for one agent.
• Do not create or mutate GitHub issues, acquire leases, create per-item branches or worktrees, commit, push, open a PR, merge, or publish evidence.

A request to explain, inspect, or draft is read-only. A request to create or plan local work authorizes only the work-set documents and index. A request to implement, resume, continue, or finish with local-work authorizes the in-scope code and test changes plus work-set updates. It does not authorize commit, push, publication, destructive cleanup, or unrelated fixes.

Prepare the work set