planlisted
Install: claude install-skill LucasSantana-Dev/sharekit
# plan
Use planning only when it actually reduces risk.
## Steps
1. Read local guidance and active handoff.
2. Pull only the context needed for the task.
3. State goal, in-scope, and out-of-scope.
4. Break work into short phases.
5. Give each phase exact file paths (**Files Touched**) and a runnable **Verify** command — agents execute paths and commands, not prose.
6. Write the plan to `.claude/plans/` or `.agents/plans/`.
## Rules
- Keep phases small enough to finish without drifting.
- Note what would cause replanning.
- If work is already partly done, document the current state before planning the rest.
- Prefer the provided plan template (`references/plan-template.md`).
- Don't over-specify: too much detail buries priorities. File paths, scope, verification — then stop.
- **AC contract (team/product work):** when a spec exists in `specs/`, every task must carry its requirement ID (`REQ-n`) and the EARS acceptance criteria (`AC-x.y`, GIVEN/WHEN/THEN) that prove it done — the AC-coverage gate (`hooks/check-ac-coverage.sh`) fails untraceable tasks. Acceptance criteria map 1:1 to eval tasks where an eval suite exists.
- **Spec-anchored:** extend the existing spec for a feature rather than creating a new one (`specs/<feature>/`; template at `specs/_template/`). The spec directory, not personal memory, is the cross-operator source of truth.
## Extend vs new plan
Before writing, scan `.claude/plans/` and `.agents/plans/`:
- Existing plan covers same scope AND ≤30 days ol