## Agent feature workflow (specship)

For any non-trivial change, follow `.specship/skills/WORKFLOW.md` and the
per-stage playbooks in `.specship/skills/ss-<stage>/SKILL.md`.

Stages (every skill folder is `ss-`-prefixed):

- `ss-spec` → understand the request → `tasks/TASK-<ID>/spec.md`
- `ss-plan` → design steps → `tasks/TASK-<ID>/plan.md`
- `ss-coding` → implement (TDD or conventional), tick `S#`
- `ss-review` → run the full gate, verify every `AC#` → `tasks/TASK-<ID>/review.md`
- `ss-debug` → when a defect appears, log it in `tasks/TASK-<ID>/debug.md`, fix, resume
- `ss-ship` → autopilot: given a feature request, run spec → plan → coding → review end-to-end
- `ss-resume-task`, `ss-pause-task`, `ss-archive-task` → task lifecycle without losing pipeline state
- `ss-research` → answer an external-fact question with the strongest search tool available (specialized MCP search first) → complete cited report in `docs/research/`

The `ss-` prefix names skills only — `stage:`/`artifacts:` values in `task.md`
stay unprefixed (`spec`, `plan`, `coding`, `review`, `debug`, `done`).

Maintain shared state in `tasks/TASK-<ID>/`: read `task.md` first, update it last,
keep IDs stable, and timestamp every log entry as `YYYY-MM-DD HH:MM +TZ` using
`date`. Only the pipeline stages and lifecycle skills write to `tasks/`. Don't
run git add/commit/push unless asked.