rad-portfolio

Create and maintain portfolio documents tracking multi-iteration design initiatives across sessions.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-portfolio-metalhexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rad-portfolio
Source: https://github.com/MetalHexx/rad-orc-marketplace/tree/main/claude-plugin/skills/rad-portfolio
Command: npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-portfolio-metalhexx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running design initiatives spanning many sessions lose context between conversations. This Skill keeps a portfolio's five core documents (root map, decisions, technical design, ground truth, iterations timeline) accurate and current so multi-session work never has to be re-litigated. ## Core Features & Use Cases - Portfolio Orientation: Look up any portfolio via the radorch CLI, read its root document map, and instantly see where a long-running initiative stands. - Automatic Document Maintenance: Detects when decisions converge, facts are verified, or iterations ship, and offers to scribe updates into the correct document. - Iteration Debriefing: Records what an iteration actually delivered versus what it was scoped to deliver, flagging drift and unauthorized work. - Use Case: You return to a three-month-old design initiative and ask where it stands. The Skill reads the portfolio's root document, reconciles shipped iterations against the timeline, and offers to debrief anything delivered but never folded back. ## Quick Start Ask the agent to show the current status of your portfolio or to create a new portfolio for a long-running initiative you are starting.

Frequently Asked Questions about rad-portfolio

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

FAQPage Schema
How do I track a long-running project across multiple AI sessions?▼

Create a portfolio, which stores the initiative's state in five markdown documents: a root map, decisions ledger, technical design, ground truth, and iterations timeline. Each session starts by reading the root document to orient instantly without re-explaining context.

How do I record what an iteration actually delivered?▼

Invoke the debrief mode with the project name. It compares the iteration's scoped bullets against its requirements, amendments, and final review, then writes the delta to ground truth, the iterations timeline, and the root document, flagging any unscoped work.

When should I use a portfolio instead of a single project?▼

Use a portfolio only for genuinely long-running initiatives spanning many iterations and sessions. A single project with phases gains nothing from a portfolio and only adds document maintenance overhead.

Does the skill write documents automatically without asking?▼

No. It detects when something has converged or shipped and offers to scribe it, but one approval authorizes exactly one writing pass. Debrief mode is the exception: it writes first and asks questions afterward.

What are the limitations of the debrief mode?▼

Debrief cannot create timeline entries retroactively, since scope written after the fact is self-confirming. It also never writes to the decisions ledger or technical document, flagging contradictions as open questions instead.