Skills Reference

Documents a project's architecture for AI assistants by writing compact architecture.md files into a .rpiv/guidance/ shadow tree alongside the source.

Documents a project's architecture for AI assistants by writing compact `CLAUDE.md` files inline next to the source they describe.

One-pass replacement for `design` + `plan` — decomposes a feature into vertical slices with developer micro-checkpoints and emits an implement-ready phased plan in a single run.

Regenerates the `[Unreleased]` section of every affected `CHANGELOG.md` from commits + uncommitted hunks, classified by Conventional Commit prefix. Monorepo-aware, idempotent.

Reads a diff, branch, or PR through Quality · Security · Dependencies lenses with parallel specialist agents and returns one cited report under `.rpiv/artifacts/reviews/`.

Reads the working tree, groups related changes into logical commits, and writes descriptive messages in the repo's style — never amends, never adds AI attribution.

Compresses the current session's task, decisions, in-flight changes, and open questions into a single handoff document that a fresh session can pick up cold.

Decomposes a complex feature into vertical slices and produces a design artifact (architecture decisions, slice breakdown, file map) that the planning skills consume.

Interviews you one question at a time to capture feature intent (Goals · Non-Goals · Functional Requirements · Acceptance Criteria · Decisions) into a Feature Requirements Document the research skill consumes.

Compares 2–4 candidate approaches across precedent-fit, integration risk, migration cost, verification cost, and novelty, then recommends one — ready to feed `design` or `blueprint`.

Forces a deliberate aesthetic *before* a line of frontend code — scans the project's style system, asks only what isn't settled, and injects tailored design guidelines plus an anti-slop list.

Executes an approved phased plan one phase at a time, applies changes, runs each phase's success criteria, and only advances when they pass.

One-shot move from inline `CLAUDE.md` files to the `.rpiv/guidance/` shadow tree — transforms cross-references along the way.

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.

Sequences a design artifact into parallelized atomic phases with explicit success criteria, written to `.rpiv/artifacts/plans/`.

Answers structured research questions about a codebase by formulating trace-quality questions, dispatching parallel analysis agents, and synthesizing a cited research document under `.rpiv/artifacts/research/`.

Reads a handoff document, re-verifies the working tree against it, and continues exactly where the previous session stopped.

Surgically updates an existing implementation plan after review feedback, mid-implementation discoveries, or scope changes — preserves structure rather than rewriting.

Independently re-runs each phase's success criteria against the working tree and emits a pass/fail validation report — catches half-finished phases the implement loop missed.

Generates flow-based manual test cases for one feature by analyzing implementing code in parallel — emits the feature suite plus a regression suite and a project-wide coverage map.