---
trigger: always_on
description: Staged specship workflow with shared task state on disk
---

## 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` (spec → plan →
coding → review; debug as needed; `ss-ship` runs the full flow end-to-end).
Every skill folder is `ss-`-prefixed; the `stage:`/`artifacts:` values in
`task.md` are not.

Maintain shared state in `tasks/TASK-<ID>/`: read `task.md` first, update it last,
keep IDs stable (`R#`, `AC#`, `S#`, `BUG#`), and timestamp every log entry as
`YYYY-MM-DD HH:MM +TZ` using `date`.

Read `docs/onboarding/how-to-code.md` before writing code and
`docs/onboarding/source-structure.md` to decide where changes belong; run
`ss-explore-source` to generate those docs if missing. Only pipeline stages and
lifecycle skills (`ss-pause-task`/`ss-archive-task`/`ss-resume-task`) write to `tasks/`.
Don't run git add/commit/push unless asked.