← ClaudeAtlas

rnd-narrativelisted

Generate a development narrative for a pipeline session — a prose story of what was built, key decisions, obstacles, insights, and what's left.
oleksify/rnd-framework · ★ 0 · Data & Documents · score 75
Install: claude install-skill oleksify/rnd-framework
# R&D Framework: Development Narrative Generate a human-readable narrative of a pipeline session from its artifacts. Use this after a session ends, or anytime you want to understand what happened in a past run. ## Step 1: Resolve the Session Parse `$ARGUMENTS` to find the target session: - **If `$ARGUMENTS` is a session ID** (matches `YYYYMMDD-HHMMSS-XXXX` format): resolve it to `<base>/sessions/<session-id>/` - **If `$ARGUMENTS` is empty**: check for an active session first. If none, use the most recent session directory (latest by name sort under `<base>/sessions/`). ```bash RND_DIR=$("${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh") ``` If no session directory is found, tell the user: "No pipeline sessions found for this project. Run `/rnd-framework:rnd-start` first." and stop. ## Step 2: Read Artifacts Read all available artifacts from the session directory. Not all may exist — some sessions produce fewer artifacts than full pipeline runs. Read what's there: - `$RND_DIR/protocol.md` — task tree, pre-registrations, dependencies, schedule - `$RND_DIR/builds/T*-manifest.md` — what each builder produced (use Glob: `$RND_DIR/builds/*-manifest.md`) - `$RND_DIR/verifications/T*-verification.md` — verifier verdicts and findings (use Glob: `$RND_DIR/verifications/*-verification.md`) - `$RND_DIR/iteration-log.md` — iteration cycles, if any - `$RND_DIR/integration/wave-*-report.md` — integration results (use Glob: `$RND_DIR/integration/*-report.md`) - `$RND_DIR/design-spec.md` — arch