You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/requirements-refiner/SKILL.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ description: "Requirements Refiner: Iteratively questions the user to clarify va
10
10
2.**Iterative Elicitation**:
11
11
- Identify gaps, ambiguities, or assumptions.
12
12
- Ask a set of numbered clarifying questions.
13
+
- For **each question**, provide 2–4 concrete answer options labeled (a), (b), (c), etc., and mark one as **"Recommended"** with a brief rationale. The user can pick an option, combine options, or provide their own answer.
13
14
- Wait for the user's response.
14
15
- Repeat this step until the requirements are clear and complete.
15
16
3.**Consolidate**:
@@ -25,5 +26,22 @@ description: "Requirements Refiner: Iteratively questions the user to clarify va
25
26
## Key Behaviors
26
27
-**Iterative Approach**: Do not rush to the final output. Prioritize clarity over speed.
27
28
-**Probe Deeply**: Ask about edge cases, error states, and user roles.
29
+
-**Suggest, Don't Just Ask**: Every clarifying question must include concrete options with a recommended choice. Base recommendations on the project context, industry best practices, and the elicitation standards. This helps the user make faster decisions and reduces back-and-forth.
28
30
-**Datetime-stamped Folders**: Use the current UTC time in `YYYYMMDDHHmmss` format as the folder prefix.
29
31
-**Output Format**: The final output must be saved as `feature-docs/{YYYYMMDDHHmmss}-{feature-slug}/REQUIREMENTS.md`.
32
+
33
+
## Question Format Example
34
+
35
+
```
36
+
1. **Who should be able to trigger this workflow?**
37
+
(a) Only admin users
38
+
(b) Any authenticated user
39
+
(c) Both authenticated users and external API consumers
40
+
→ **Recommended: (b)** — Most workflows in this system are user-initiated; restricting to admins adds friction without clear security benefit.
41
+
42
+
2. **How should the system handle partial failures?**
43
+
(a) Fail the entire operation and roll back
44
+
(b) Continue processing remaining items and report failures at the end
45
+
(c) Retry failed items up to N times, then report
46
+
→ **Recommended: (c)** — Retries with a cap balance reliability with predictable completion times.
0 commit comments