expand

Expand terse workflow artifacts into readable English for human review.

2|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/FourthWiz/quoin --skill expand-fourthwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expand
Source: https://github.com/FourthWiz/quoin/tree/main/quoin/skills/expand
Command: npx skills add https://github.com/FourthWiz/quoin --skill expand-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expands compressed (terse) workflow artifacts back to human-readable English for faster comprehension and review.

Core Features & Use Cases

  • Dispatches to Tier 1 English display, Class B built-in summary ("For human" blocks), and Tier 3 LLM re-expansion with an opt-in save.
  • Follows a defined 7-step pipeline to resolve paths, check content, and apply the appropriate expansion path safely.
  • Supports architecture v3 style artifacts (current-plan.md, architecture.md, review-*.md) and other Class B artifacts for human consumption.

Quick Start

Run /expand <path> to re-expand a terse artifact into readable English.

Frequently Asked Questions about expand

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

FAQPage Schema
How do I expand terse workflow artifacts back into readable English?

To expand terse workflow artifacts, run /expand <path> to process compressed files like current-plan.md and architecture.md back into human-readable English using a 7-step expansion pipeline.

What is LLM re-expansion for terse artifacts?

LLM re-expansion is a Tier 3 process that transforms compressed workflow artifacts into readable English summaries. It includes an opt-in save feature to store the expanded output for later human review.

How do I convert compressed architecture notes to a human-readable format?

You convert compressed architecture notes to a human-readable format by dispatching them through tiered content handling, which checks for Class B built-in summary blocks before applying LLM re-expansion.

Does the artifact expansion pipeline support v2 and v3 format notes?

Yes, the artifact expansion pipeline supports both v2 and v3 format notes. It safely resolves paths and applies the appropriate expansion path to Class B artifacts requiring human-readable verification.

When should I avoid using LLM re-expansion for workflow artifacts?

You should avoid using LLM re-expansion for contract-approval tasks. The expansion pipeline includes specific safeguards to prevent misuse during contract approval and verification processes.

Can I review current-plan.md files without reading the terse source code?

Yes, you can review current-plan.md files without reading the terse source by running the expand command. It processes Class B artifacts into human-readable summaries for faster comprehension and review.