elaborate

Writes implement-ready code for one phase of a synthesized plan into a per-phase elaboration artifact.

730|137|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill elaborate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elaborate
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/elaborate
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill elaborate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jiti, @juicesharp/rpiv-workflow.

What problem does it solve?

Turning a high-level implementation plan into actual code is slow and error-prone when one agent tries to write every phase at once. This Skill converts a single phase of a synthesized plan into concrete, paste-ready code blocks, running as one lane of a parallel fanout so multiple phases are elaborated concurrently without conflicting edits.

Core Features & Use Cases

  • Single-phase code generation: Reads the full plan plus the real code the phase touches, then emits a code-bearing replacement for exactly one ## Phase N: section to .rpiv/artifacts/elaborations/.
  • Parallel-safe self-check: Applies drafted code blocks at their real anchor positions, runs the project's scoped type-check and lint commands, then reverts the tree byte-identical so sibling phase lanes are never corrupted.
  • Deterministic splice integration: Emits a document whose heading and filename pair to the plan so the stitch-elaborations script can fold per-phase elaborations back into the plan for grading.
  • Use Case: After a synthesize step produces a multi-phase refactor plan, a workflow fanout dispatches one elaborate unit per phase; each unit grounds its code in the current tree, verifies it compiles, and hands a ready-to-implement phase section to the downstream implement step.

Quick Start

Dispatch this Skill with a plan path and phase heading, for example: elaborate .rpiv/artifacts/plans/my-plan.md Phase 2: Add retry logic.

Frequently Asked Questions about elaborate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I elaborate a single phase of an implementation plan?

Dispatch the Skill with the plan path followed by the phase heading, in the form `<plan-path> Phase N: <title>`. It reads the full plan and the real code that phase touches, then writes one elaboration document to `.rpiv/artifacts/elaborations/` containing paste-ready code blocks.

How does the elaborate skill avoid conflicts when phases run in parallel?

Each unit restricts itself to a write-scope: only the files its phase's Changes section names. Its self-check applies drafted code, runs scoped checks, then reverts with git restore and rm so the tree returns byte-identical to its pre-probe state, never touching sibling-owned files.

Can I use the elaborate skill standalone instead of in a fanout?

It is designed as a fanout unit dispatched once per phase after a synthesize step, not as a standalone tool. The output filename and heading are built for the deterministic stitch-elaborations script, and cross-phase interfaces are assumed to come from the plan's Synthesis Notes.

What happens if the elaboration self-check finds errors?

Only errors whose file paths fall inside the phase's write-scope are attributed to the unit; cross-file noise from sibling lanes is ignored. The drafted code blocks are fixed and re-verified, and any git residue after the revert is a blocking error that stops emission.

Does the elaborate skill modify the repository code directly?

No lasting edits are made. The only tree mutation is a transient, fully reverted probe used to verify the drafted code compiles at its real anchor; the elaboration document is the sole output, and a later implement step applies the code.