wf-shape

Shape raw project inputs into brief, breadboard, risk register, and PRD artifacts.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill wf-shape
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-shape
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/02-shape/wf-shape
Command: npx skills add https://github.com/marchatton/agent-skills --skill wf-shape

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms raw ideas, notes, or bug reports into a structured, de-risked project packet (brief, breadboard, risks, spikes) ready for planning or development.

Core Features & Use Cases

  • Project Scoping: Clearly defines project goals, scope (in/out), and top risks.
  • Artifact Generation: Creates essential documents like brief.md, breadboard-pack.md, risk-register.md, and prd.md/prd.json.
  • Risk Management: Identifies, assesses, and plans mitigation for project risks.
  • Use Case: You have a new feature idea with scattered notes. Use wf-shape to consolidate these into a clear brief, identify potential roadblocks, and define the core components needed, making it ready for the next stage of development.

Quick Start

Use the wf-shape skill to shape the raw notes into a project brief and risk register.

Frequently Asked Questions about wf-shape

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

FAQPage Schema
How do I turn scattered feature ideas and raw notes into a project brief?

To turn scattered feature ideas into a project brief, consolidate raw notes into a structured packet that defines goals, scope, and core components. This de-risks the project by identifying potential roadblocks early.

What is the best way to manage project scope and identify risks before development?

The best way to manage project scope and identify risks is by generating a de-risked packet containing a brief, breadboard, and risk register. This explicitly defines in-scope and out-of-scope elements while planning mitigations for top risks.

How do I generate a risk register and PRD from messy bug reports?

Generate a risk register and PRD from messy bug reports by shaping raw inputs through iterative refinement. This assesses and plans mitigation for project risks while producing essential documentation artifacts like prd.md.

Does project shaping require iterative refinement before planning?

Yes, project shaping requires iterative refinement through oracle passes to ensure readiness for planning. This explicit refinement process guarantees the generated project packet is fully de-risked and de-scoped before development handoffs.

What documentation artifacts do I need for de-risked project scoping?

For de-risked project scoping, you need artifacts like brief.md, breadboard-pack.md, risk-register.md, and prd.md. These documents consolidate raw ideas into a clear, structured packet ready for the next development stage.