Define problem statements with boundaries and success criteria.
npx skills add https://github.com/rolopez23/agent-harness --skill problem-spec
Please help me install this Agent Skill. Skill: problem-spec Source: https://github.com/rolopez23/agent-harness/tree/main/.claude/skills/problem-spec Command: npx skills add https://github.com/rolopez23/agent-harness --skill problem-spec
This Skill helps teams articulate the problem upfront, ensuring everyone aligns on the goal, scope, and success criteria before designing a solution.
Provide a concise problem statement for a given feature or task, including boundaries and success metrics.
High-intent search queries and answers about installing and using this skill.
To define a clear problem statement for vague requirements, articulate the project scope, identify boundaries, and establish concrete acceptance criteria before any design work begins.
Aligning stakeholders on project scope requires producing a structured problem definition that explicitly identifies interfaces, actors, triggers, and concrete success metrics.
Writing acceptance criteria for unclear success boundaries involves defining problem constraints and boundary definitions upfront to ensure the solution scope is measurable and agreed upon.
You should clarify problem definitions before starting software design whenever stakeholders disagree, requirements lack specificity, or success criteria remain ambiguous to prevent misaligned solutions.
Yes, problem specification identifies interfaces, actors, and triggers within a project to ensure all participants align on the goal and scope before the design phase starts.
Problem specification works for conflicting stakeholder requirements by structuring the problem statement with explicit constraints and boundaries, ensuring everyone aligns on the goal before designing a solution.
jfrometaClarify vague product and feature requests through Socratic questioning.
hacketConvert Obsidian WikiLinks to GitHub-compatible Markdown links.
ImaginerLabsExecutes approved software development stories with test-driven workflows and CI integration.
Nir-BhayGuide backlog refinement sessions using the DEEP framework and Planning Poker.
