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
{{ message }}
Repository navigation
Commit ca87e9e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/prompts/clarify.prompt.md
+45-44Lines changed: 45 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,56 +77,56 @@ Execution steps:
77
77
- Information is better deferred to planning phase (note internally)
78
78
79
79
3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:
80
-
- Maximum of 5 total questions across the whole session.
81
-
- Each question must be answerable with EITHER:
82
-
* A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR
83
-
* A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words").
80
+
- Maximum of 5 total questions across the whole session.
81
+
- Each question must be answerable with EITHER:
82
+
- A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR
83
+
- A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words").
84
84
- Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.
85
85
- Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.
| C | <OptionCdescription> | (add D/E as needed up to 5)|
99
+
| Short | Provide a different short answer (<=5 words) | (Include only if free-form alternative is appropriate)|
100
+
101
+
- For short‑answer style (no meaningful discrete options), output a single line after the question: `Format: Short answer (<=5 words)`.
102
+
- After the user answers:
103
+
- Validate the answer maps to one option or fits the <=5 word constraint.
104
+
- If ambiguous, ask for a quick disambiguation (count still belongs to same question; do not advance).
105
+
- Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.
106
+
- Stop asking further questions when:
107
+
- All critical ambiguities resolved early (remaining queued items become unnecessary), OR
108
+
- User signals completion ("done", "good", "no more"), OR
109
+
- You reach 5 asked questions.
110
+
- Never reveal future queued questions in advance.
111
+
- If no valid questions exist at start, immediately report no critical ambiguities.
112
112
113
113
5. Integration after EACH accepted answer (incremental update approach):
114
-
- Maintain in-memory representation of the spec (loaded once at start) plus the raw file contents.
115
-
- For the first integrated answer in this session:
116
-
* Ensure a `## Clarifications` section exists (create it just after the highest-level contextual/overview section per the spec template if missing).
117
-
* Under it, create (if not present) a `### Session YYYY-MM-DD` subheading for today.
118
-
- Append a bullet line immediately after acceptance: `- Q: <question> → A: <final answer>`.
119
-
- Then immediately apply the clarification to the most appropriate section(s):
120
-
* Functional ambiguity → Update or add a bullet in Functional Requirements.
121
-
* User interaction / actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.
122
-
* Data shape / entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.
123
-
* Non-functional constraint → Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).
124
-
* Edge case / negative flow → Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).
125
-
* Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.
126
-
- If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.
127
-
- Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).
128
-
- Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.
129
-
- Keep each inserted clarification minimal and testable (avoid narrative drift).
114
+
- Maintain in-memory representation of the spec (loaded once at start) plus the raw file contents.
115
+
- For the first integrated answer in this session:
116
+
- Ensure a `## Clarifications` section exists (create it just after the highest-level contextual/overview section per the spec template if missing).
117
+
- Under it, create (if not present) a `### Session YYYY-MM-DD` subheading for today.
118
+
- Append a bullet line immediately after acceptance: `- Q: <question> → A: <final answer>`.
119
+
- Then immediately apply the clarification to the most appropriate section(s):
120
+
- Functional ambiguity → Update or add a bullet in Functional Requirements.
121
+
- User interaction / actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.
122
+
- Data shape / entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.
123
+
- Non-functional constraint → Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).
124
+
- Edge case / negative flow → Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).
125
+
- Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.
126
+
- If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.
127
+
- Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).
128
+
- Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.
129
+
- Keep each inserted clarification minimal and testable (avoid narrative drift).
130
130
131
131
6. Validation (performed after EACH write plus final pass):
132
132
- Clarifications session contains exactly one bullet per accepted answer (no duplicates).
@@ -147,12 +147,13 @@ Execution steps:
147
147
- Suggested next command.
148
148
149
149
Behavior rules:
150
+
150
151
- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: "No critical ambiguities detected worth formal clarification." and suggest proceeding.
151
152
- If spec file missing, instruct user to run `/specify` first (do not create a new spec here).
152
153
- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).
Copy file name to clipboardExpand all lines: .github/prompts/constitution.prompt.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,16 +14,16 @@ Follow this execution flow:
14
14
15
15
1. Load the existing constitution template at `.specify/memory/constitution.md`.
16
16
- Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
17
-
**IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
17
+
**IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
18
18
19
19
2. Collect/derive values for placeholders:
20
20
- If user input (conversation) supplies a value, use it.
21
21
- Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
22
22
- For governance dates: `RATIFICATION_DATE` is the original adoption date (if unknown ask or mark TODO), `LAST_AMENDED_DATE` is today if changes are made, otherwise keep previous.
23
23
-`CONSTITUTION_VERSION` must increment according to semantic versioning rules:
24
-
* MAJOR: Backward incompatible governance/principle removals or redefinitions.
25
-
* MINOR: New principle/section added or materially expanded guidance.
Copy file name to clipboardExpand all lines: .github/prompts/specify.prompt.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ The text the user typed after `/specify` in the triggering message **is** the fe
13
13
Given that feature description, do this:
14
14
15
15
1. Run the script `.specify/scripts/bash/create-new-feature.sh --json "$ARGUMENTS"` from repo root and parse its JSON output for BRANCH_NAME and SPEC_FILE. All file paths must be absolute.
16
-
**IMPORTANT** You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
16
+
**IMPORTANT** You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
17
17
2. Load `.specify/templates/spec-template.md` to understand required sections.
18
18
3. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
19
19
4. Report completion with branch name, spec file path, and readiness for the next phase.
0 commit comments