§ reference · skill

outline-test-cases

Discovers testable features (Frontend-First) and lays out a per-feature folder under `.rpiv/test-cases/` with `_meta.md` scope decisions — ready for `write-test-cases` to fill in.

arguments target-directory

§ 01 · purpose

Purpose

Maps the project's testable surface before any test cases are authored. outline-test-cases discovers routes, endpoints, and existing tests, then emits a folder skeleton (one folder per feature) with metadata so write-test-cases can pick up scope-aware. Re-runs are incremental — prior outlines guide smarter checkpoints.

§ 02 · when to use

When to use it

You're starting test-case authoring for a project and need the full feature inventory.
An existing outline is stale and you want a diff-based refresh.
Skip when you only need test cases for a single feature you've already scoped.

§ 03 · inputs

Inputs

Name	Required	Source
`target-directory`	no	CLI argument or current working directory
existing `.rpiv/test-cases/` outline	no	Auto-detected — triggers Incremental mode when present

§ 04 · outputs

Outputs

Artifact	Path	Format
Per-feature outline folders	`.rpiv/test-cases/<feature>/_meta.md`	markdown with scope decisions + routes + endpoints
Project summary	`.rpiv/test-cases/README.md`	markdown

§ 05 · key steps

Key steps

Detect Fresh vs Incremental mode Why: An existing outline isn't ignored — it seeds the next run. Incremental mode highlights what changed since the last outline, so re-runs aren't wholesale rewrites.
Parallel discovery — routes · frontend HTTP call sites · backend controllers · existing test cases Why: Four codebase-locator / test-case-locator agents run concurrently. Frontend-First means routes drive the feature list; backend controllers and HTTP call sites are evidence, not the starting point.
Cross-reference findings into a feature list Why: Frontend routes are validated against the navigation menu, enriched via API call mapping, and cross-checked against backend controllers. Catches features the team navigates to but no backend serves (or vice versa).
Diff-based checkpoint (Incremental mode only) Why: Shows added/removed features against the last outline, so the developer signs off only on the delta — not the entire list every time.
Write per-feature _meta.md + project README Why: Each feature gets its own folder with metadata write-test-cases reads as warm-start context. The project README is the index — newcomers and write-test-cases runs both consult it.

§ 06 · related skills

downstream write-test-cases