Dobeu-tech-eco

action-items

Show open action items (Secrets, Decisions, Handoff, Deploy, Promotions) with age, owner and resolving command; mark done, add, or assign. Use when asked what is left, what is blocked on me, action items, or to hand this to another agent.

Dobeu-tech-eco 0 Updated 1w ago
GitHub

Install

npx skillscat add dobeu-tech-eco/dts2-marketplace/action-items

Install via the SkillsCat registry.

SKILL.md

Directory edition: do not run bundled scripts or hooks, a package launcher, or a download piped into a shell. Do not read tokens or credential files from the machine. Carry out the step with Read, Edit, Grep, Glob, and git or gh, and write the files the step names.

Action items — what is still open and who owns it

Reads .harness/action-items.md; handoff briefs under .harness/handoff/ appear as Handoff rows. All reading and writing goes through scripts/action-items.py; never edit the table by hand.

List (default)

  1. Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/action-items.py" <repo> list. In workspace mode, run it per repo.
  2. Print the items grouped in this order: Secrets, Decisions, Handoff, Deploy, Promotions. One line each: <id> <item> — owner <owner or unassigned>, <age_days>d — <resolve_command>. Skip empty groups. No open items → say No open action items.
  3. Row ids are the group letter plus the row position: S1 secret, D1 decision, H1 handoff, Y1 deploy, P1 promotion. Ids stay stable when rows are marked done.
  4. resolve_command is what the user runs next:
    • Secrets → run add secret NAME (/dt:run add secret NAME)
    • Promotions → learn promote <id> (/dt:learn)
    • Handoff → open .harness/handoff/<agent>/<n>.md
    • Deploy and Decisions → run (deploy watch and plan checkpoint respectively)

Parked sections

Sections the run parked appear after the groups: the list also shows every ## Sections row of .harness/end-state.md with status blocked, one line each: section <#> <name> — blocked (<action-item id>). The same lines appear in the handoff file's ## Open items.

Subcommands

  • done <row>: action-items.py <repo> done S1. Marks the row done. For a secret, check presence first as in /dt:run (add secret NAME); never mark a secret done without it.
  • add <group> <text>: action-items.py <repo> add Decisions "pick a domain". Appends an open row with today's date and prints its id. For Secrets the text is the variable name.
  • assign <row> <agent>: action-items.py <repo> assign S1 codex. Sets the owner column. The owner is the agent or person who acts next.

After done, add or assign, refresh the pass-off file: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-write.py" <repo>.

Guardrails

  • For secrets, never print a value: names, status and commands only. Text that looks like NAME=value is redacted by the script.
  • Only the user marks Decisions done; an agent assigns or adds but never decides for them.
  • Never edit .env, push, or run a resolve command for the user. Print it.