todo-enforcer
Enforce the per-open-item todo contract (strict CLI-only mutation via `npm run todos --`; no hand-edits to `*.todo.json`) so tracked agent work stays focused, isolated, and linked to an open item.
- License 许可
- MPL-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- todo-enforcer
- description
- Enforce the per-open-item todo contract (strict CLI-only mutation via `npm run todos --`; no hand-edits to `*.todo.json`) so tracked agent work stays focused, isolated, and linked to an open item.
03 SKILL.md 正文
Todo Enforcer
Enforce the work-tracking methodology.
Read and follow .pi/skills/todo-contract/SKILL.md before deciding whether work may proceed.
Rules (Hard — No Exceptions)
- No open item, no tracked work: If non-trivial tracked work has no owning
OI-####, stop and create or promote one first. - One todo list per open item, CLI only: Tracked execution work lives in
.agents/open-items/items/OI-####.todo.jsonand is mutated only vianpm run todos -- …(seetodo-contract§ CLI tooling). Never hand-edit*.todo.json; never create a new.todo.mdsidecar or repo-rootTODO.md. - No mixed workstreams: Do not place tasks for multiple open items into one sidecar.
- Complete before branching: If a task is
in_progress, finish it or explicitly mark itblockedbefore moving to another task (set-task-status). - Discover → report or spawn: If you discover meaningful new work for a different concept,
add-taskonly if it advances the same OI; otherwise create or promote a separate open item with its own sidecar. - Keep tracking current: Mark tasks
in_progress,blocked, orcompletedas soon as their state changes (CLI only). - Missing verb → escalate, not bypass: If the operation you need isn’t exposed by the CLI, stop and report to the operator so the CLI is extended. Do not hand-edit the JSON as a workaround.
Enforcement questions
Ask before acting:
- What is the owning
OI-####? - Am I mutating only that item's sidecar via
npm run todos --? - Is this task already reflected (
npm run todos -- show/list)? - Am I about to create work that really belongs to a different open item?
Encountering legacy artifacts
- Stray
OI-####.todo.md: Treat as drift; surface vianpm run open-items -- validateand delete (or replace vianpm run todos -- create OI-####+add-taskcalls). - Repo-root
TODO.md: Treat as a pre-contract artifact; split its content into the appropriateOI-####sidecars (add-task) and delete the file. - Mixed or ownerless legacy todo files: Reject further tracked execution against them until they are split per owning OI.
Reporting format
TODO ENFORCEMENT REPORT:
Open item: OI-####
Current task: T-XXX [description]
Issue: [missing open item / mixed workstreams / out-of-scope discovery / malformed todo / hand-edited JSON / missing CLI verb]
Impact: [why work should pause or split]
Recommended next action: [create open item / split todo / add-task via CLI / ask operator to extend CLI]
04 同仓库更多 Skills
structured-output-repair
暂无简介
version-release
Use when the user asks to bump/increment the package version, prepare a release, produce changelog/release notes, or decide whether a change should be called out in the changelog.
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
todo-monitor
Create and advance a per-open-item agent todo list using the `npm run todos --` CLI without pausing after each task. Follows todo-contract (strict CLI-only mutation) and todo-enforcer rules.
todo-hard-stop
Execute a per-open-item todo list via the `npm run todos --` CLI under the canonical todo contract, pausing after each completed task for operator feedback.
todo-contract
Defines the canonical per-open-item todo JSON sidecar, strict CLI-only mutation, status vocabulary, and linkage rules.