propose-work

Files (1)

• SKILL.md

SKILL.md (first lines)

# Propose work

Tool: `work_propose`

## When

New independently acceptable work discovered during a run, or a scoped follow-up that is not yet committed.

## How

- `work_search` first — abort if a duplicate title/scope exists.
- Include `team`, `title`, and `description`.
- **Hierarchy (`parent_id`)**: Always pass `parent_id` (e.g. `INV-2` or parent UUID) when nesting an Issue under a Milestone or Milestone under a Project. This guarantees top-down `CONTAINS` linking and prevents relationship inversion.
- **Mandatory Structured Chinese Description**:
  Every proposal must follow the 3-section format:
  - `### 1. 目标与架构定位`: Role in system architecture, rationale.
  - `### 2. 核心功能与交付范围`: Modules, APIs, components affected.
  - `### 3. 验收标准与验证方案`: Concrete vitest/jest commands, exit 0 criteria.
- Set `repository` (e.g. `fakechris/Involute`) and `kind` (`ISSUE`, `MILESTONE`, `PROJECT`).
- **Initial Target State (`initial_state`)**:
  Always set `initial_state` to route the item to the right phase upon human commit:
  - `'REVIEW'`: For historical features or work already implemented and passing tests in the repository. When committed (via Web UI `/candidates` or batch-commit CLI), the item directly lands in **`In Review`**!
  - `'STARTED'`: For active / in-progress tasks. Lands in **`In Progress`**.
  - `'UNSTARTED'`: For pending unstarted tasks (default). Lands in **`Ready`**.
- Candidates do **not** enter the ready queue until committed by a human (via Web UI `/candidates` or `pnpm candidates:batch-commit`).
- **Bugs are not candidates.** File them with MCP `work_file_bug` (required `priority` 1–4, `steps_to_reproduce` and `acceptance`). That call commits the bug directly and starts the SLA (1 Urgent 24h, 2 High 48h, 3/4 = 7 days). `work_propose` with `labels: ['bug']` does the same, and **refuses** if parent, priority, steps or acceptance are missing. Do not put Type: Bug through `/candidates`.

## Rules

- Never use propose as a TODO dump.
- Candidate `initial_state` CANNOT be `CANCELED`, and CANNOT be `DONE` unless the item is a research ISSUE (`labels: ['research']`, Type: Research, INV-912) — that one lands in Done when a person commits it. Everything else stops at `In Review`; `Done` is human-gated.
- Agents do not unilaterally `work_commit` or reject candidates via MCP — humans commit.
- **Status is read, not remembered**: A person may silently commit or decline your proposed candidates at any time (in the Web UI `/candidates` or via batch-commit CLI) without telling you in chat. Before mentioning or reporting the status of any previously proposed candidate, always read `agent_inbox` (`notifications`: `work.committed` / `work.rejected`, then `ack` handled IDs) or check `commitmentStatus` via `work_get_context` — never assume it is still `CANDIDATE` from session memory.
- For unplanned hotfixes / bugfixes: run `pnpm hotfix:reflex` to propose and link with `DISCOVERED_DURING`.
- All production code changes must link to a committed `INV-xxx` (enforced by Layer 1 Git guardrail).

From fakechris/Involute, Apache-2.0.

More from fakechris/Involute