Skip to content

tim-hub/powerball-harness / harness/skills/harness-plan

harness-plan

Verified

Plans and tracks tasks in .claude/harness/plans.json. Use when creating plans, adding tasks, updating markers, checking progress, or brainstorming an idea into tasks.

FileKindSize
SKILL.mdskill md8.0 KB
references/add.mdmarkdown2.7 KB
references/archive.mdmarkdown1.8 KB
references/brainstorm.mdmarkdown3.5 KB
references/create.mdmarkdown15.6 KB
references/planning-quality.mdmarkdown7.6 KB
references/ralph-tasks.mdmarkdown2.8 KB
references/sync.mdmarkdown6.4 KB
references/task-fields.mdmarkdown2.1 KB
references/update.mdmarkdown2.3 KB
templates/plans-md-template.mdmarkdown1.4 KB

references/update.md

View on GitHub
# update Subcommand — Update Marker

Changes a task's status via `harness plan-cli update`. The SSOT is `.claude/harness/plans.json`; never edit a status cell in `Plans.md` markdown.

## Syntax

```
harness-plan update [task-name|task-number] [WIP|done|blocked|TODO]
```

## Marker Mapping

| Command | `--status` value |
|---------|------------------|
| `WIP` | `cc:WIP` |
| `done` | `cc:done` |
| `blocked` | `blocked` |
| `TODO` | `cc:TODO` |

For full status marker semantics — including the `cc:done [hash]` artifact notation and the required reason annotation for `blocked` — see [task-fields.md](${CLAUDE_SKILL_DIR}/references/task-fields.md) ("Status Markers" section).

## Flow

1. Locate the target task by name or task ID (e.g. `2.3`) using `harness plan-cli list`/`get`.
   - Ambiguity → list candidates and ask the user.
   - Not found → abort with a clear "task not found" message.
2. Apply the status change: `harness plan-cli update <task-id> --status <mapped-status>`.
3. For `blocked`, prompt the user for a one-line reason and pass it via `--reason` (required for `blocked`):
   `harness plan-cli update <task-id> --status blocked --reason "waiting on external API spec"`
4. For `done`, pass the short git hash via `--hash` (required for `cc:done`) when a recent commit can be unambiguously attributed to this task:
   `harness plan-cli update <task-id> --status cc:done --hash a1b2c3d`
5. The CLI performs an atomic write to `plans.json` without reordering.

## Notes

- Marker updates **never** change phase ordering. Use `harness-plan archive` to remove fully completed phases.
- Use `harness-plan sync` (not `update`) when discrepancy detection across many tasks is needed — `update` is for a single deliberate marker change.

## Agent Delegation

This subcommand can be delegated to the `harness-planner` agent (Haiku, low effort) when a caller (skill or agent) wants to mark a task without running the skill flow inline.

Request shape (`planner-request.v1`):

```json
{
  "schema_version": "planner-request.v1",
  "operation": "update",
  "task_id": "98.3",
  "marker": "done",
  "commit_hash": "a1b2c3d"
}
```

For `marker: "blocked"` the caller must also supply a `reason` field. See [`harness/agents/harness-planner.md`](${CLAUDE_SKILL_DIR}/../../agents/harness-planner.md).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall