test-plan

rafaie/test-plan

Planning

1 installs

About

Read AGENTS.md, codex.toml (if present), and the target work item folder spec/features/<work-id>-<slug>/.
- <work-id> must use S-<stream>-<nnn> (example: S-core-001) for new work.
- For legacy single-file specs, read the matching file under spec/features/.
- Source acceptance criteria from feature.md (or the legacy single-file spec).
Convert acceptance criteria into a test matrix:
- Unit tests (fast, isolated)
- Integration tests (component boundaries)
- End-to-end / scenario tests (happy path + key edge cases)
- Negative/error cases (validation, permissions, timeouts, etc.)
Decide what to mock vs run for real (with rationale).
Update test-plan.md with:
- Test cases mapped to ACs
- Test data/fixtures needed
- Any required test hooks/utilities
- Smoke plan fields:
  - scenario ID/name
  - fixture path
  - expected output shape (schema and invariants)
  - pass/fail mode (schema/invariants only, or schema/invariants/golden)
  - runtime constraints (mode, network/env, time budget, request/token budget)
  - artifact path expectation (artifacts/smoke/...)
End by recommending write-tests.
- Output exactly:
  - Next recommended skill:
  - Run $write-tests <work-id> to implement the planned unit/integration/edge-case tests.
- Replace <work-id> with the real ID from the target folder (example: S-core-001).
- Do not use markdown links or absolute file paths in this recommendation.