1## Why23Agents and humans can currently read OpenSpec artifacts, but they need a uniform write-side lifecycle surface to capture ideas, enrich them, create/promote changes, move task work toward done, and archive/unarchive completed work without manually editing files. A noun-action tool naming convention makes this surface easier for agents and humans to discover and use consistently.45## What Changes67- Rename the idea lifecycle tools to noun-action names:8 - `openspec_idea_create`9 - `openspec_idea_enrich`10 - `openspec_idea_promote`11- Add task lifecycle tools:12 - `openspec_task_list`13 - `openspec_task_set_status`14- Add change lifecycle tools:15 - `openspec_change_create`16 - `openspec_change_promote`17 - `openspec_change_archive`18 - `openspec_change_unarchive`19- Keep lifecycle operations explicit: creating ideas, enriching ideas, promoting ideas, creating changes, promoting changes, updating tasks, and archiving/unarchiving changes remain separate reviewable steps.20- Use deterministic filesystem behavior, safe slug/change-id generation, collision handling, and structured JSON responses so agents can chain the tools reliably.2122## Capabilities2324### New Capabilities25- None.2627### Modified Capabilities28- `agent-tools`: Add write-side idea, task, and change lifecycle tools using uniform noun-action naming.29- `dashboard-sources`: Ensure dashboard/source scans can reflect ideas and changes created or moved by agent tools without extra manual refresh assumptions.3031## Impact3233- Affected tool registration and schemas:34 - `plugin.yaml`35 - `__init__.py`36 - `schemas.py`37 - `tools.py`38- Affected OpenSpec filesystem conventions:39 - `openspec/ideas/<slug>.md`40 - `openspec/changes/<change-id>/proposal.md`41 - `openspec/changes/<change-id>/tasks.md`42 - `openspec/changes/<change-id>/specs/**/spec.md`43 - `openspec/changes/archive/<change-id>/`44- Affected dashboard behavior only insofar as tool-created and tool-moved artifacts must appear in existing source scans.45- Tests should cover naming exposure, slug/collision handling, invalid workdirs, idea creation/enrichment/promotion, change creation/promotion/archive/unarchive, task listing/status updates, validation of promoted scaffolds, and refusal to overwrite existing artifacts unless explicitly allowed.