define

Generate a project-definition.md from a validated concept brief.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill define-withpiper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define
Source: https://github.com/withpiper/pipekit/tree/main/skills/define
Command: npx skills add https://github.com/withpiper/pipekit --skill define-withpiper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill a validated concept into a complete project definition to guide strategy, planning, and execution across stages, roles, and success criteria.

Core Features & Use Cases

  • Produces a structured project-definition.md from a validated concept brief.
  • Defines a scalable stage breakdown, roles, workflows, non-functional requirements, and success criteria to inform tech decisions and roadmaps.
  • Serves as the authoritative reference for alignment between concept validation and delivery planning.

Quick Start

Place a concept-brief.md in your project root and run /define to generate a complete project-definition.md.

Frequently Asked Questions about define

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

FAQPage Schema
How do I turn a validated concept brief into a complete project definition?

To create a complete project definition from a validated concept brief, you distill the brief into stage planning, roles, workflows, and success criteria across the definition process.

What is the best way to outline project workflows and stage breakdowns from a concept brief?

Outlining project workflows and stage breakdowns involves distilling your concept brief to define scalable stages, identify key roles, and specify integration requirements for delivery planning.

Do I need a specific input format to generate a project-definition.md file?

Yes, you need to place a validated concept-brief.md file in your project root directory to generate the complete project-definition.md output.

How does defining project roles and success criteria guide tech decisions and roadmaps?

Defining project roles and success criteria guides tech decisions by structuring non-functional requirements and workflows within the project definition, serving as the authoritative alignment reference.

Can I use this project definition approach for aligning concept validation with delivery planning?

Yes, you can use this project definition approach to align concept validation with delivery planning by establishing an authoritative reference that satisfies requirements across phases three through ten.

What limitations exist when distilling a concept brief into project stages and roles?

A limitation when distilling a concept brief into project stages and roles is that the process strictly requires a validated concept-brief.md as input to produce the final project-definition.md output.