One-click install
npx skills add https://github.com/marchatton/agent-skills --skill wf-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-plan
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/03-plan/wf-plan
Command: npx skills add https://github.com/marchatton/agent-skills --skill wf-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill transforms a shaped project packet (brief, breadboard, risks, spikes) into a commit-ready, deep project plan, ensuring clarity and avoiding context rot before development begins.

Core Features & Use Cases

  • Automated Plan Generation: Creates a structured plan.md from input documents.
  • Gap Analysis: Identifies missing perimeter or top risks, routing back to the shaping phase if necessary.
  • Research Integration: Incorporates local and external research, including institutional learnings and concrete file paths.
  • Spec Hardening: Addresses edge cases, failure modes, and security concerns.
  • Commit Gate: Ensures all criteria (AC, verification, sequencing, etc.) are met before approval.
  • Handoff Ready: Prepares a summary for the next development phase.

Quick Start

Use the wf-plan skill to create a project plan from the dossier located at /path/to/project/dossier.

Frequently Asked Questions about wf-plan

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

FAQPage Schema
How do I generate a deep project plan from a specification brief?

Project plan generation requires a shaped project packet including a brief, breadboard, risks, and spikes. The system ingests these to create a structured plan, perform research, and harden the specification before a go/no-go decision.

What is specification hardening in the development lifecycle?

Specification hardening identifies edge cases, failure modes, and security concerns within your project plan. It ensures acceptance criteria are measurable, verification is planned, and rollout and rollback procedures are defined before development begins.

How do I ensure my project risks and spikes are fully addressed before development?

Gap analysis identifies missing perimeter or top risks, routing back to the shaping phase if necessary. The plan integrates local and external research, including institutional learnings and concrete file paths, to address risks comprehensively.

Can I use workflow automation to plan rollout and rollback procedures?

Workflow automation creates a commit-ready project plan that explicitly defines both rollout and rollback procedures. This ensures verification is planned and sequencing is explicit before a final go/no-go approval decision is made.

What is a shaped project packet and do I need one to create a project plan?

A shaped project packet is a dossier containing a brief, breadboard, risks, and spikes. You must provide this input before plan generation begins, as the system routes back to the shaping phase if critical documents are missing.

What are the limitations of automated project planning from a dossier?

Automated project planning cannot proceed without a complete shaped project packet. If the gap analysis detects missing perimeter or top risks, the workflow halts and routes back to the shaping phase to ensure specification completeness.