name	spec-clarify
description	Ask targeted questions to clarify scope, edge cases, and acceptance before coding.
compatibility	Designed for skills-compatible coding agents.
metadata	{"category":"clarification","tags":["requirements","scope","ambiguity"],"applies_to":["frontend","backend","cli","scripts","mobile"],"priority":"core","agents":["universal","codex"],"repo_shapes":["app","library","cli","scripts","monorepo"]}

Spec Clarify

Objective

Surface ambiguities and edge cases early.
Confirm inputs, outputs, and constraints before implementation.

When to use

Requirements are vague, conflicting, or incomplete.
Before starting on a new feature or significant change.

Inputs

User request and any provided specs.
AGENTS.md and applicable rules.
Existing behavior inferred from code/tests.

Process

Restate the goal and current understanding.
List assumptions explicitly.
Ask precise questions on inputs/outputs, data shapes, edge cases, and metrics.
Highlight risks of proceeding without answers.
Propose a minimal path once questions are resolved.

Outputs

Concise list of questions and assumptions.
Risks of proceeding without answers.
Suggested next step once clarified.

Edge cases

If blocking ambiguity exists, do not proceed to implementation; ask first.
Keep questions specific and answerable; avoid broad surveys.

Más de este repositorio

mismo repositorio

analyze

leanbusqts/agent47

Understand the current state, flows, and issues before making changes.

2026-04-302

cli-design

leanbusqts/agent47

Design or refine command surfaces, output contracts, and preview flows for CLI tools.

2026-04-302

implement

leanbusqts/agent47

Deliver a scoped change that meets the stated requirements with minimal surface area.

2026-04-302

optimize

leanbusqts/agent47

Improve performance or resource usage with evidence and clear trade-offs.

2026-04-302

plan

leanbusqts/agent47

Create a concise plan with risks and checkpoints before executing any changes.

2026-04-302

refactor

leanbusqts/agent47

Improve structure and clarity without changing externally visible behavior.

2026-04-302

name	spec-clarify
description	Ask targeted questions to clarify scope, edge cases, and acceptance before coding.
compatibility	Designed for skills-compatible coding agents.
metadata	{"category":"clarification","tags":["requirements","scope","ambiguity"],"applies_to":["frontend","backend","cli","scripts","mobile"],"priority":"core","agents":["universal","codex"],"repo_shapes":["app","library","cli","scripts","monorepo"]}

Spec Clarify

Objective

Surface ambiguities and edge cases early.
Confirm inputs, outputs, and constraints before implementation.

When to use

Requirements are vague, conflicting, or incomplete.
Before starting on a new feature or significant change.

Inputs

User request and any provided specs.
AGENTS.md and applicable rules.
Existing behavior inferred from code/tests.

Process

Restate the goal and current understanding.
List assumptions explicitly.
Ask precise questions on inputs/outputs, data shapes, edge cases, and metrics.
Highlight risks of proceeding without answers.
Propose a minimal path once questions are resolved.

Outputs

Concise list of questions and assumptions.
Risks of proceeding without answers.
Suggested next step once clarified.

Edge cases

If blocking ambiguity exists, do not proceed to implementation; ask first.
Keep questions specific and answerable; avoid broad surveys.