issue-shaping

Shape rough requests into problem statements with constraints and acceptance criteria.

1|1|Updated Apr 18, 2026

Search Tags:#planning #github #blueprint #risk-management #brainstorm #acceptance-criteria #issue-shaping

Ready to run

npx skills add https://github.com/emmepra/ora-et-labora --skill issue-shaping

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-shaping
Source: https://github.com/emmepra/ora-et-labora/tree/main/skills/issue-shaping
Command: npx skills add https://github.com/emmepra/ora-et-labora --skill issue-shaping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating rough requests into a well-scoped plan by creating a durable problem statement, constraints, risks, and acceptance criteria before any code is written.

Core Features & Use Cases

Converts vague input into a concrete issue contract that can be shaped into .project/ artifacts.
Produces a brainstorm placeholder (00_brainstorm.md) and a ready-to-run GitHub issue body with clear acceptance criteria.
Guides feasibility assessment and blueprint fit to prevent scope creep and misalignment.

Quick Start

Turn rough requests into a shaped issue with constraints, acceptance criteria, and a brainstorm placeholder.

Frequently Asked Questions about issue-shaping

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

FAQPage Schema

How do I turn rough project requests into actionable GitHub issues?▼

To turn rough requests into actionable GitHub issues, you must shape the input into a clear problem statement with constraints, risks, and acceptance criteria before writing any code. This prevents scope creep and ensures alignment.

What is issue shaping in software planning?▼

Issue shaping is a planning workflow that converts vague input into a concrete issue contract. It produces a durable problem statement, constraints, risks, acceptance checks, and a brainstorm placeholder to guide development.

How do I write acceptance criteria for a poorly defined feature request?▼

Writing acceptance criteria for a poorly defined request requires applying a blueprint fit workflow to assess feasibility. This process shapes the rough input into a ready-to-run GitHub issue body with clear, actionable acceptance checks.

When should I create a brainstorm file during project planning?▼

You should create a brainstorm file, such as `00_brainstorm.md`, when a rough request requires shaping into a structured plan. The blueprint fit workflow decides when this placeholder is needed to prevent misalignment.

Does issue shaping work for risk management and scope creep prevention?▼

Issue shaping works for risk management by guiding feasibility assessment and blueprint fit before development begins. By creating a durable problem statement with explicit constraints, it actively prevents scope creep and misalignment.

Can I use issue shaping to generate project artifacts from a vague idea?▼

Yes, you can use issue shaping to generate project artifacts from a vague idea. It shapes the input into a complete, ready-to-action artifact set that can be integrated into `.project/` directories for development planning.