spec

Define problem, scope, and acceptance criteria into a /plan artifact.

Updated Jan 4, 2026

Search Tags:#planning #handoff #scope #acceptance-criteria #define #problem-statement

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill spec-yeachan05

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/spec
Command: npx skills add https://github.com/YeaChan05/Remittance --skill spec-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DEFINE-stage planning helps teams lock the problem statement, scope, and acceptance criteria before design or implementation, reducing misalignment and rework.

Core Features & Use Cases

Clear problem statements for stakeholders and product teams.
Capture scope, constraints, success criteria, and open questions to guide implementation.
Produce a ready-to-hand off /plan artifact for teams to execute.

Quick Start

Provide a DEFINE plan by restating the user request as a problem statement with scope, constraints, and acceptance criteria.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I define project scope and acceptance criteria before implementation?▼

To define project scope and acceptance criteria, you restate the user request as a problem statement, capture constraints, and lock success metrics. This produces a ready-to-use plan artifact to guide downstream design and implementation.

What is a problem statement and why does it matter for project planning?▼

A problem statement is a clear summary of the issue a project aims to solve for stakeholders. Defining it during early planning reduces team misalignment and minimizes rework before design or implementation begins.

How do I prepare a plan artifact for stakeholder handoff?▼

Prepare a plan artifact for handoff by documenting the problem statement, scope, acceptance criteria, and open questions. This ready-to-use output ensures execution teams have clear directives for the next implementation phase.

When do I need to lock scope and constraints during early planning?▼

You need to lock scope and constraints during the DEFINE stage of early planning. Finalizing these elements before ideation prevents misalignment and ensures all stakeholders agree on the project boundaries.

What is the best way to capture open questions for a project request?▼

The best way to capture open questions is to log them alongside the problem statement and success criteria in a structured plan artifact. This tracks unresolved constraints for the team to address during implementation handoff.

Can I use this approach for stakeholder alignment without a full design phase?▼

Yes, you can use this approach for stakeholder alignment without a full design phase. It applies to early ideation when a problem statement and success criteria must be locked prior to committing to design or implementation.