spec-the-problem

Prompt users to define problem, constraints, and success criteria before coding.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/argen/hornero --skill spec-the-problem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-the-problem
Source: https://github.com/argen/hornero/tree/main/skills/spec-the-problem
Command: npx skills add https://github.com/argen/hornero --skill spec-the-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that a comprehensive problem statement, including constraints and success criteria, is established before proceeding with implementation, aligning with the 'Spec problems, not solutions' principle by Chris MDP.

Core Features & Use Cases

  • Problem Speculation: Guides the user to articulate the true problem, not a solution.
  • Constraints & Success Criteria: Facilitates the definition of non-negotiable requirements and measurable outcomes.
  • Use Case: Before implementing a new feature, use this Skill to understand the root cause of the issue and what defines success.

Quick Start

Use the spec-the-problem skill to define the problem, constraints, and success criteria for implementing a retry mechanism for failed uploads.

Frequently Asked Questions about spec-the-problem

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

FAQPage Schema
How do I define problem constraints and success criteria before coding a new feature?

Problem speculation involves articulating the true root cause of an issue rather than jumping straight to coding a fix. It guides you to outline the exact problem, preventing wasted effort on building solutions that do not address the underlying need.

What is the best way to scope requirements for implementing a retry mechanism for failed uploads?

The best way to scope requirements for a retry mechanism is to establish a detailed problem statement outlining the upload failures, defining non-negotiable constraints, and specifying measurable success criteria before any implementation begins.

When do I need pre-implementation problem scoping for software engineering tasks?

You need pre-implementation problem scoping whenever you are preparing to implement a new feature or design decision. It is required to align your work with the principle of specifying problems, not solutions, ensuring measurable outcomes are defined beforehand.

How does specifying a problem instead of a solution improve code safety?

Specifying a problem instead of a solution improves code safety by forcing a focus on non-negotiable constraints and measurable outcomes before implementation. This prevents over-engineering and ensures the deployed code directly addresses the root cause.

Can I use this approach for design decisions without writing actual code?

Yes, you can apply this problem specification approach to design decisions without writing code. It facilitates outlining the problem, constraints, and success criteria, ensuring that architectural and design choices are validated against measurable outcomes.