itemslisted

The credo work-item model, where the FOLDER an item file lives in is the single source of truth for its status, gated by a hard Definition of Done. Use whenever you create, update, or track a work item; whenever you decide whether something is "done" and may move to 2_done/; whenever you move an item between status folders (clarify, go, done, archived, parked); whenever new code might be unwired; or when someone asks where a task stands. This is the credo task system: .credo/items/ replaces ad-hoc task lists. Applies inside subagents too - if you build or complete work, record and gate it as an item.
Marcel-Bich/marcel-bich-claude-marketplace · ★ 13 · AI & Automation · score 80

Install: claude install-skill Marcel-Bich/marcel-bich-claude-marketplace

# items - the credo work-item model A work item is a single Markdown file under `.credo/items/`. The **folder the file lives in is the only source of truth for its status**. There is no status field, no marker, no task-tracker entry - an item changes status by physically moving between folders. This is deliberate anti-drift: multiple status sources drift out of sync, one physical location cannot. `.credo/items/` IS the task system; do not mirror items into a separate task list. "Do not mirror" does NOT mean "never use the harness task list at all" - it means no FULL items live there; references to items are fine (see "Harness task-list vs .credo items" below). > **Task backend.** If the task backend is `gsd` (set in `.credo/config` as `task_backend`, or via the `CREDO_TASK_BACKEND` env override; resolve with `credo-config.sh backend`), the credo item system is inactive - GSD's > phases are the task system for this project. Do NOT create or move `.credo/items/`; use > GSD's workflow instead. This skill applies only when the backend is `credo` (the default) > or `none`. ## Status = folder (the only truth) The folder tree (created by `credo-init`) and what each folder means: ``` .credo/items/ 1_todo/ 1_clarify/ open questions - needs the user, NOT buildable yet 2_go/ clarified and approved - buildable (go-gate: only 2_go is buildable) 3_blocked/ GO'd but hard-blocked by another (unbuilt) credo item; auto-returns to 2_go on unblock 2_done/