@jeancodogno/specforce-kit 0.1.4 → 0.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/index.js +0 -0
- package/package.json +12 -28
- package/.geminiignore +0 -15
- package/.github/workflows/ci.yml +0 -101
- package/.github/workflows/release.yml +0 -51
- package/.golangci.yml +0 -17
- package/.goreleaser.yaml +0 -39
- package/.rgignore +0 -13
- package/.specforce/config.yaml +0 -32
- package/.specforce/docs/.gitkeep +0 -0
- package/.specforce/docs/architecture.md +0 -98
- package/.specforce/docs/engineering.md +0 -80
- package/.specforce/docs/governance.md +0 -30
- package/.specforce/docs/memorial.md +0 -44
- package/.specforce/docs/principles.md +0 -31
- package/.specforce/docs/security.md +0 -31
- package/.specforce/docs/ui-ux.md +0 -129
- package/.specforce/specs/.gitkeep +0 -0
- package/AGENTS.md +0 -36
- package/CONTRIBUTING.md +0 -81
- package/Makefile +0 -49
- package/assets/logo-header.png +0 -0
- package/assets/logo.png +0 -0
- package/docs/artifacts.md +0 -41
- package/docs/cli.md +0 -73
- package/docs/configuration.md +0 -50
- package/docs/getting-started.md +0 -110
- package/docs/supported-tools.md +0 -14
- package/go.mod +0 -35
- package/go.sum +0 -61
- package/src/cmd/specforce/main.go +0 -23
- package/src/cmd/specforce/main_test.go +0 -7
- package/src/internal/agent/artifacts/constitution/architecture.yaml +0 -70
- package/src/internal/agent/artifacts/constitution/engineering.yaml +0 -52
- package/src/internal/agent/artifacts/constitution/governance.yaml +0 -41
- package/src/internal/agent/artifacts/constitution/memorial.yaml +0 -55
- package/src/internal/agent/artifacts/constitution/principles.yaml +0 -54
- package/src/internal/agent/artifacts/constitution/security.yaml +0 -47
- package/src/internal/agent/artifacts/constitution/ui-ux.yaml +0 -158
- package/src/internal/agent/artifacts/spec/design.yaml +0 -50
- package/src/internal/agent/artifacts/spec/requirements.yaml +0 -48
- package/src/internal/agent/artifacts/spec/tasks.yaml +0 -55
- package/src/internal/agent/compatibility_test.go +0 -120
- package/src/internal/agent/cwd_test.go +0 -9
- package/src/internal/agent/embed.go +0 -19
- package/src/internal/agent/integration_test.go +0 -138
- package/src/internal/agent/kit/agents/product-analyst.yaml +0 -31
- package/src/internal/agent/kit/agents/technical-developer.yaml +0 -28
- package/src/internal/agent/kit/agents/technical-project-planner.yaml +0 -30
- package/src/internal/agent/kit/agents/technical-qa-engineer.yaml +0 -36
- package/src/internal/agent/kit/agents/technical-solution-architect.yaml +0 -32
- package/src/internal/agent/kit/commands/archive.yaml +0 -25
- package/src/internal/agent/kit/commands/constitution.yaml +0 -132
- package/src/internal/agent/kit/commands/implement.yaml +0 -96
- package/src/internal/agent/kit/commands/spec.yaml +0 -94
- package/src/internal/agent/kit/instructions/archive.md +0 -68
- package/src/internal/agent/kit/kit.yaml +0 -111
- package/src/internal/agent/kit/skills/opportunity-framing/SKILL.yaml +0 -56
- package/src/internal/agent/kit/skills/pragmatic-product-owner/SKILL.yaml +0 -58
- package/src/internal/agent/kit/skills/pragmatic-product-owner/references/spec-artifacts.yaml +0 -38
- package/src/internal/agent/kit/skills/spec-clarification-interview/SKILL.yaml +0 -52
- package/src/internal/agent/kit/skills/task-atomic-decomposition/SKILL.yaml +0 -137
- package/src/internal/agent/kit/skills/task-atomic-decomposition/references/roadmap-patterns.yaml +0 -103
- package/src/internal/agent/kit_manifests_test.go +0 -58
- package/src/internal/agent/manifest.go +0 -15
- package/src/internal/agent/registry.go +0 -69
- package/src/internal/agent/registry_test.go +0 -51
- package/src/internal/agent/translator.go +0 -334
- package/src/internal/agent/translator_test.go +0 -734
- package/src/internal/cli/archive.go +0 -91
- package/src/internal/cli/archive_test.go +0 -67
- package/src/internal/cli/cli.go +0 -259
- package/src/internal/cli/cli_test.go +0 -130
- package/src/internal/cli/cobra/archive.go +0 -26
- package/src/internal/cli/cobra/console.go +0 -21
- package/src/internal/cli/cobra/constitution.go +0 -44
- package/src/internal/cli/cobra/dummy_test.go +0 -7
- package/src/internal/cli/cobra/implementation.go +0 -50
- package/src/internal/cli/cobra/init.go +0 -23
- package/src/internal/cli/cobra/install.go +0 -21
- package/src/internal/cli/cobra/root.go +0 -47
- package/src/internal/cli/cobra/spec.go +0 -91
- package/src/internal/cli/console.go +0 -48
- package/src/internal/cli/constitution.go +0 -190
- package/src/internal/cli/constitution_test.go +0 -50
- package/src/internal/cli/implementation.go +0 -153
- package/src/internal/cli/implementation_test.go +0 -165
- package/src/internal/cli/spec.go +0 -369
- package/src/internal/cli/spec_test.go +0 -85
- package/src/internal/constitution/registry.go +0 -139
- package/src/internal/constitution/registry_test.go +0 -97
- package/src/internal/constitution/status.go +0 -70
- package/src/internal/constitution/status_test.go +0 -160
- package/src/internal/core/blueprint.go +0 -49
- package/src/internal/core/blueprint_test.go +0 -58
- package/src/internal/core/config.go +0 -124
- package/src/internal/core/config_test.go +0 -145
- package/src/internal/core/constants.go +0 -13
- package/src/internal/core/errors.go +0 -31
- package/src/internal/core/errors_test.go +0 -48
- package/src/internal/core/hooks.go +0 -89
- package/src/internal/core/hooks_test.go +0 -51
- package/src/internal/core/kit.go +0 -15
- package/src/internal/core/kit_test.go +0 -65
- package/src/internal/core/path.go +0 -115
- package/src/internal/core/path_test.go +0 -101
- package/src/internal/core/ui.go +0 -19
- package/src/internal/installer/dependencies.go +0 -23
- package/src/internal/installer/install.go +0 -89
- package/src/internal/installer/installer.go +0 -45
- package/src/internal/installer/installer_test.go +0 -96
- package/src/internal/project/agents_md.go +0 -108
- package/src/internal/project/agents_md_test.go +0 -101
- package/src/internal/project/bootstrapper.go +0 -64
- package/src/internal/project/bootstrapper_test.go +0 -89
- package/src/internal/project/detector.go +0 -35
- package/src/internal/project/detector_test.go +0 -96
- package/src/internal/project/refresh_integration_test.go +0 -86
- package/src/internal/project/service.go +0 -93
- package/src/internal/project/service_test.go +0 -135
- package/src/internal/spec/archive.go +0 -49
- package/src/internal/spec/archive_test.go +0 -55
- package/src/internal/spec/discovery.go +0 -53
- package/src/internal/spec/discovery_test.go +0 -60
- package/src/internal/spec/implementation.go +0 -296
- package/src/internal/spec/implementation_test.go +0 -253
- package/src/internal/spec/registry.go +0 -142
- package/src/internal/spec/registry_test.go +0 -105
- package/src/internal/spec/scanner.go +0 -219
- package/src/internal/spec/scanner_test.go +0 -243
- package/src/internal/spec/service.go +0 -157
- package/src/internal/spec/service_test.go +0 -238
- package/src/internal/spec/status.go +0 -94
- package/src/internal/spec/status_test.go +0 -146
- package/src/internal/spec/tasks.go +0 -103
- package/src/internal/spec/tasks_test.go +0 -137
- package/src/internal/tui/components.go +0 -132
- package/src/internal/tui/console.go +0 -247
- package/src/internal/tui/console_test.go +0 -19
- package/src/internal/tui/constitution.go +0 -36
- package/src/internal/tui/constitution_test.go +0 -32
- package/src/internal/tui/implementation.go +0 -151
- package/src/internal/tui/logo.go +0 -89
- package/src/internal/tui/multiselect.go +0 -199
- package/src/internal/tui/progressbar.go +0 -37
- package/src/internal/tui/progressbar_test.go +0 -30
- package/src/internal/tui/spec.go +0 -35
- package/src/internal/tui/spinner.go +0 -66
- package/src/internal/tui/terminal.go +0 -18
- package/src/internal/tui/theme.go +0 -125
- package/src/internal/tui/ui.go +0 -52
|
@@ -1,132 +0,0 @@
|
|
|
1
|
-
description: Initialize, update, orchestrate, and generate the project's Core Constitution
|
|
2
|
-
artifacts.
|
|
3
|
-
mapping:
|
|
4
|
-
open-code:
|
|
5
|
-
name: spf.constitution
|
|
6
|
-
kilo-code:
|
|
7
|
-
name: spf.constitution
|
|
8
|
-
kimi-code:
|
|
9
|
-
name: spf.constitution
|
|
10
|
-
content: |
|
|
11
|
-
# TASK: Manage Project Constitution
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
You are the Specforce Orchestrator. Your objective is to initialize missing Constitution
|
|
15
|
-
files or update existing ones within the `.specforce/docs/` directory. The Constitution
|
|
16
|
-
defines the absolute rules, architecture, and boundaries for the project.
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
**CRITICAL RULE:** You MUST NOT hallucinate technical decisions, frameworks, or
|
|
20
|
-
business rules. You must interrogate the user for missing context or explicit changes.
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
## Execution Flow
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
### 1. Scope & Status Discovery
|
|
27
|
-
|
|
28
|
-
- Analyze the user''s input to determine their intent: **Initialize** missing artifacts,
|
|
29
|
-
or **Update** specific existing ones.
|
|
30
|
-
|
|
31
|
-
- Execute the following command to get the current state of the constitution:
|
|
32
|
-
|
|
33
|
-
```bash
|
|
34
|
-
|
|
35
|
-
specforce constitution status --json
|
|
36
|
-
|
|
37
|
-
```
|
|
38
|
-
|
|
39
|
-
- **If Initializing:** Target all artifacts where `"exists": false`.
|
|
40
|
-
|
|
41
|
-
- **If Updating:** Target only the specific artifacts the user requested to modify.
|
|
42
|
-
If their request is ambiguous, ask them which artifact they want to update.
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
### 2. Artifact Processing Loop
|
|
46
|
-
|
|
47
|
-
For each targeted artifact, process them sequentially (one by one). DO NOT attempt
|
|
48
|
-
to modify all of them at the same time.
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
**A. Load Context:**
|
|
52
|
-
|
|
53
|
-
- Execute the command below to get the schema and instructions for the specific
|
|
54
|
-
artifact:
|
|
55
|
-
|
|
56
|
-
```bash
|
|
57
|
-
|
|
58
|
-
specforce constitution artifact <slug> -json
|
|
59
|
-
|
|
60
|
-
```
|
|
61
|
-
|
|
62
|
-
- **If Updating:** You MUST read the current contents of the existing artifact file
|
|
63
|
-
first to understand the established rules before making changes.
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
**B. Dynamic Skill & Persona Adoption:**
|
|
67
|
-
|
|
68
|
-
- Analyze the `description` and `instruction` fields from the JSON payload. Based
|
|
69
|
-
on the domain, search your available skills/sub-agents and adopt the posture of
|
|
70
|
-
the highest-level expert for that domain (e.g., "Chief Information Security Officer"
|
|
71
|
-
for security, "Solutions Architect" for architecture).
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
**C. Information Gathering (Tool Discovery):**
|
|
75
|
-
|
|
76
|
-
- Analyze the JSON `instruction`, `template`, and (if updating) the existing file
|
|
77
|
-
content.
|
|
78
|
-
|
|
79
|
-
- Scan your available environment tools for the capability to prompt the user for
|
|
80
|
-
input or ask a question.
|
|
81
|
-
|
|
82
|
-
- Interrogate the user to gather the missing context or to understand the exact
|
|
83
|
-
modifications they want to make.
|
|
84
|
-
|
|
85
|
-
- *Constraint:* Consolidate your questions into a single interaction. Do not proceed
|
|
86
|
-
until the user provides the answers.
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
**D. Artifact Generation/Modification:**
|
|
90
|
-
|
|
91
|
-
- Once the user provides the context, generate or rewrite the markdown content.
|
|
92
|
-
|
|
93
|
-
- You MUST strictly adhere to the JSON `template` structure.
|
|
94
|
-
|
|
95
|
-
- **If Updating:** Seamlessly integrate the user''s new rules while preserving existing
|
|
96
|
-
decisions that were not meant to be changed.
|
|
97
|
-
|
|
98
|
-
- *Constraint:* Replace all bracketed placeholders. Do NOT leave any empty templates.
|
|
99
|
-
|
|
100
|
-
- Write the completed content to the exact `path` specified in the JSON using your
|
|
101
|
-
file-writing tool.
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
### 3. Verification & Handoff
|
|
105
|
-
|
|
106
|
-
- After writing the artifact, loop back to **Step 2** for the next targeted artifact.
|
|
107
|
-
|
|
108
|
-
- Once all targeted artifacts are processed, output a final summary to the user
|
|
109
|
-
detailing what was created or updated.
|
|
110
|
-
|
|
111
|
-
**Format:**
|
|
112
|
-
```markdown
|
|
113
|
-
**Action:** [Initialized | Updated] Constitution
|
|
114
|
-
**Location:** `.specforce/docs/`
|
|
115
|
-
|
|
116
|
-
**Artifacts:**
|
|
117
|
-
- `[artifact_name].md`: [Brief 1-line description of the core rule established or updated]
|
|
118
|
-
|
|
119
|
-
Constitution aligned and ready.
|
|
120
|
-
|
|
121
|
-
> Run `/spec` to start planning a new feature.```
|
|
122
|
-
|
|
123
|
-
## Guardrails
|
|
124
|
-
|
|
125
|
-
- **Zero Hallucination:** If the user gives a vague answer, you must ask for clarification
|
|
126
|
-
before writing or updating.
|
|
127
|
-
|
|
128
|
-
- **Template Integrity:** Your output MUST match the layout, headings, and markdown
|
|
129
|
-
blocks of the `template` field, even when performing an update.
|
|
130
|
-
|
|
131
|
-
- **Environment Agnostic:** Rely on the dynamic JSON payloads from the CLI. Do not
|
|
132
|
-
assume the existence of specific artifact names beforehand.
|
|
@@ -1,96 +0,0 @@
|
|
|
1
|
-
description: "Execute the Implementation Roadmap autonomously using strict TDD, dynamic agent discovery, terminal commands, and holistic QA validation."
|
|
2
|
-
mapping:
|
|
3
|
-
open-code:
|
|
4
|
-
name: spf.implement
|
|
5
|
-
kilo-code:
|
|
6
|
-
name: spf.implement
|
|
7
|
-
kimi-code:
|
|
8
|
-
name: spf.implement
|
|
9
|
-
content: |
|
|
10
|
-
# TASK: Senior Implementation Orchestration
|
|
11
|
-
|
|
12
|
-
You are the Senior Implementation Orchestrator. Your mission is to execute the implementation roadmap for a feature, strictly following the defined sequence, writing code, verifying it via Test-Driven Development (TDD), and performing a final Quality Assurance validation.
|
|
13
|
-
|
|
14
|
-
**CRITICAL RULE:** You are a deterministic execution engine. You MUST NOT deviate from the action steps, hallucinate new features, or skip verifications.
|
|
15
|
-
|
|
16
|
-
## The Execution Protocol (Sequential Batching)
|
|
17
|
-
|
|
18
|
-
You MUST execute the following phases in order. Do NOT query the implementation status repeatedly.
|
|
19
|
-
|
|
20
|
-
### 1. Initialization & Roadmap Mapping (DO THIS ONLY ONCE)
|
|
21
|
-
Execute the following command EXACTLY ONCE at the start of your session to get the full roadmap:
|
|
22
|
-
|
|
23
|
-
`specforce implementation status <slug> --json`
|
|
24
|
-
|
|
25
|
-
- Analyze the JSON output and identify ALL tasks where the `state` is `pending` (or anything other than `finished` or `x`).
|
|
26
|
-
- Map these pending tasks in your internal memory in their strict sequential order.
|
|
27
|
-
- **DO NOT run the status command again during this session.**
|
|
28
|
-
|
|
29
|
-
### 2. Task Claiming & Context Loading (Iterate Internally)
|
|
30
|
-
For each pending task identified in Step 1, perform the following in order:
|
|
31
|
-
|
|
32
|
-
**A. Claim the Task:**
|
|
33
|
-
- Immediately mark the current task as in-progress:
|
|
34
|
-
|
|
35
|
-
`specforce implementation update <slug> --task <task-id> --status in-progress`
|
|
36
|
-
|
|
37
|
-
**B. Context & Target Loading:** - Review the `context` field of the task (e.g., `[REQ-1](requirements.md)`). Use your file-reading tool to read the specific sections of the files listed in the `context_files` array.
|
|
38
|
-
- If the task has a specific file `target`, use your file-reading tool to read its current state before modifying it.
|
|
39
|
-
|
|
40
|
-
**C. Dynamic Agent & Skill Discovery:**
|
|
41
|
-
- Analyze the task's `title`, `target`, and `action_steps`.
|
|
42
|
-
- You MUST perform an agent discovery step to find the ideal subagent or skill available in your tools to perform the task.
|
|
43
|
-
- **CRITICAL:** Once the best tool or subagent is identified, you must activate it or delegate the task execution to it. Be aware that different tasks will likely require different subagents.
|
|
44
|
-
|
|
45
|
-
### 3. TDD Execution (The Red/Green Cycle)
|
|
46
|
-
Operating as the specific expert, execute the `action_steps`:
|
|
47
|
-
|
|
48
|
-
**A. The Red Phase (Test First):**
|
|
49
|
-
- Implement the test code first based on the `verification` field.
|
|
50
|
-
- Execute the exact command provided in the `verification` field via terminal. It MUST fail initially (Red).
|
|
51
|
-
|
|
52
|
-
**B. The Green Phase (Implementation):**
|
|
53
|
-
- Write the implementation code in the `target` file to satisfy the test and `action_steps`.
|
|
54
|
-
- Re-run the `verification` command.
|
|
55
|
-
|
|
56
|
-
**C. Self-Healing:**
|
|
57
|
-
- If verification fails, read `stderr`, debug, and fix.
|
|
58
|
-
- Maximum 3 attempts. If it still fails, execute:
|
|
59
|
-
|
|
60
|
-
`specforce implementation update <slug> --task <task-id> --status failed`
|
|
61
|
-
|
|
62
|
-
- STOP execution immediately and ask the user for help.
|
|
63
|
-
|
|
64
|
-
### 4. Completion & Transition
|
|
65
|
-
- ONLY when the `verification` command returns a successful execution (exit code 0 / PASSED), the task is complete.
|
|
66
|
-
- Update the CLI state:
|
|
67
|
-
|
|
68
|
-
`specforce implementation update <slug> --task <task-id> --status finished`
|
|
69
|
-
|
|
70
|
-
- **CRITICAL:** Immediately proceed to Step 2 for the next mapped pending task in your memory. Do NOT run the status command.
|
|
71
|
-
- If all mapped tasks are finished, proceed to Step 5.
|
|
72
|
-
|
|
73
|
-
### 5. Final QA Validation (Holistic Review)
|
|
74
|
-
Once ALL mapped tasks are finished, perform a global QA check.
|
|
75
|
-
|
|
76
|
-
**A. Adopt QA Persona:** Switch to "Lead QA Engineer".
|
|
77
|
-
**B. Review Acceptance Criteria:** Scan `requirements.md` focusing on BDD Scenarios and Business Invariants.
|
|
78
|
-
**C. Global Verification:** Execute the project's global test suite (e.g., `go test ./...`) via the terminal to ensure no regressions exist.
|
|
79
|
-
**D. Final Report:** - If validation passes, output EXACTLY the following format:
|
|
80
|
-
**Format:**
|
|
81
|
-
```markdown
|
|
82
|
-
**Implemented:** [{FEATURE_NAME}]
|
|
83
|
-
**Tasks Completed:** [Total number of tasks, e.g., 6/6]
|
|
84
|
-
**QA Status:** [PASSED]
|
|
85
|
-
|
|
86
|
-
Implementation and QA successfully complete! All acceptance criteria have been met.
|
|
87
|
-
|
|
88
|
-
> Run `/archive` to close the lifecycle.
|
|
89
|
-
```
|
|
90
|
-
|
|
91
|
-
- If the global validation fails, output a summary of the broken holistic tests and ask the user how they would like to proceed.
|
|
92
|
-
|
|
93
|
-
## Guardrails
|
|
94
|
-
- **Terminal Truth:** Your file writes mean nothing if the terminal verification fails.
|
|
95
|
-
- **Scope Containment:** Edit ONLY the file specified in the task `target` during implementation.
|
|
96
|
-
- **No Interactive Prompts:** Ensure terminal commands use non-interactive flags (e.g., `-y`, `--quiet`).
|
|
@@ -1,94 +0,0 @@
|
|
|
1
|
-
description: "Orchestrate the creation or modification of a Feature Specification using the Specforce pipeline, performing dynamic discovery, interrogation, and strict adherence to project context."
|
|
2
|
-
mapping:
|
|
3
|
-
open-code:
|
|
4
|
-
name: spf.spec
|
|
5
|
-
kilo-code:
|
|
6
|
-
name: spf.spec
|
|
7
|
-
kimi-code:
|
|
8
|
-
name: spf.spec
|
|
9
|
-
content: |
|
|
10
|
-
# TASK: Specforce Feature Orchestration
|
|
11
|
-
|
|
12
|
-
You are the Specforce Feature Orchestrator. Your mission is to guide the user's feature request through the Spec-Driven Development (SDD) pipeline, generating or updating necessary planning artifacts based on their dependencies.
|
|
13
|
-
|
|
14
|
-
**CRITICAL RULES:**
|
|
15
|
-
1. You MUST NOT hallucinate technical decisions, business rules, or edge cases.
|
|
16
|
-
2. You MUST check the current constitution artifacts and read those relevant to the project context before generating any feature specs to ensure global alignment.
|
|
17
|
-
3. You MUST NOT enter any specialized planning or architectural design modes. Remain in your primary orchestration loop.
|
|
18
|
-
4. **NO DEVELOPMENT:** You are strictly a PLANNER. You MUST NOT write implementation code, application logic, or scripts under any circumstances. Limit your output to documentation and markdown artifacts only.
|
|
19
|
-
5. **DOCUMENTATION ONLY:** The sole purpose of this command is to document the specification. When discovering and delegating to subagents, you MUST explicitly enforce that they also ONLY write documentation and do NOT attempt to implement the feature.
|
|
20
|
-
|
|
21
|
-
## The Execution Protocol (The Pipeline)
|
|
22
|
-
|
|
23
|
-
You MUST execute this pipeline sequentially until the feature is 100% planned or the requested update is complete. Do not poll for status unnecessarily.
|
|
24
|
-
|
|
25
|
-
### 1. Discovery & Intent Clarification
|
|
26
|
-
- **Skill Discovery:** Before interacting with the user, investigate your available environment tools/skills to identify the correct tool for user interaction (e.g., `ask_user` or equivalent). You MUST use this specific tool to ask questions.
|
|
27
|
-
- Execute `specforce spec list` to see all current active specifications and avoid duplicates.
|
|
28
|
-
- Execute `specforce constitution status --json` to identify relevant project documents. Read necessary constitution artifacts to align with global project rules.
|
|
29
|
-
- Analyze the user's input. If the intent is to **Initialize** a new spec:
|
|
30
|
-
- Use your discovered user-interaction tool to ask the user clarifying questions about their intent until a clear, unambiguous idea of the feature is reached. Consolidate questions into a single interaction.
|
|
31
|
-
- Determine the `slug` for the new spec. It MUST be in `kebab-case`.
|
|
32
|
-
- Execute `specforce spec init <slug>` to create the directory.
|
|
33
|
-
- If the intent is to **Update** an existing spec, identify the specific artifact(s) to modify.
|
|
34
|
-
|
|
35
|
-
### 2. Artifact Processing (Batch Execution)
|
|
36
|
-
Do NOT continuously poll for status. Execute the following command ONCE to retrieve the current state and map out your work:
|
|
37
|
-
```bash
|
|
38
|
-
specforce spec status <slug> --json
|
|
39
|
-
```
|
|
40
|
-
- Analyze the JSON output to identify all artifacts where `"exists": false` (if Initializing) or the specific targets (if Updating).
|
|
41
|
-
- Process these required artifacts sequentially in your internal memory using the following steps for EACH artifact:
|
|
42
|
-
|
|
43
|
-
**CRITICAL BATCH INSTRUCTION:**
|
|
44
|
-
If the `status` command reveals multiple missing artifacts, you MUST process and generate ALL of them in a single, continuous execution block.
|
|
45
|
-
- DO NOT stop after generating the first artifact.
|
|
46
|
-
- DO NOT ask for user permission to continue to the next artifact.
|
|
47
|
-
- You must iterate through your internal list and write every missing file before proceeding to Step 3.
|
|
48
|
-
|
|
49
|
-
**A. Load Context:**
|
|
50
|
-
- Execute the command to get the instructions and schema for the current targeted artifact:
|
|
51
|
-
```bash
|
|
52
|
-
specforce spec artifact <artifact-name> --json
|
|
53
|
-
```
|
|
54
|
-
- **Dependency Loading:** If the artifact has a `"dependency"`, you MUST read the completed dependency file before proceeding.
|
|
55
|
-
- **Update Context:** If **Updating**, you MUST read the current contents of the existing artifact file first.
|
|
56
|
-
|
|
57
|
-
**B. Dynamic Agent Discovery:**
|
|
58
|
-
- For each artifact to be generated or updated, you MUST perform an agent discovery to find the ideal subagent to perform the task.
|
|
59
|
-
- Evaluate the available tools to find the best agent and skill for the specific artifact's domain (e.g., "Product Analyst" for requirements, "Solutions Architect" for design), and activate it. Note that different artifacts may require different subagents.
|
|
60
|
-
|
|
61
|
-
**C. Information Gathering:**
|
|
62
|
-
- Identify missing business rules or technical ambiguities. If necessary, use your user-interaction tool to clarify before writing.
|
|
63
|
-
|
|
64
|
-
**D. Artifact Generation/Modification:**
|
|
65
|
-
- Generate or rewrite the markdown content strictly adhering to the JSON `template` structure and the `instruction` rules.
|
|
66
|
-
- Replace all `{PLACEHOLDERS}`. Do not leave any empty templates.
|
|
67
|
-
- Write the completed content to the exact `path` specified in the Status JSON using your file-writing tool.
|
|
68
|
-
|
|
69
|
-
### 3. Verification & Handoff
|
|
70
|
-
- ONLY after writing all planned artifacts for this session, execute `specforce spec status <slug> --json` ONE final time to verify that `"progress": 100`.
|
|
71
|
-
- **If Initializing:** Output a final summary once verified.
|
|
72
|
-
- **If Updating:** If the update invalidates downstream dependencies, ask the user if they want you to update them.
|
|
73
|
-
|
|
74
|
-
**Format:**
|
|
75
|
-
```markdown
|
|
76
|
-
**Change:** [{FEATURE_NAME}]
|
|
77
|
-
**Location:** `.specforce/specs/{FEATURE_SLUG}/`
|
|
78
|
-
|
|
79
|
-
**Artifacts:**
|
|
80
|
-
- `requirements.md`: [Brief 1-line description]
|
|
81
|
-
- `design.md`: [Brief 1-line description]
|
|
82
|
-
- `tasks.md`: [Brief 1-line description]
|
|
83
|
-
|
|
84
|
-
All artifacts created! Ready for implementation.
|
|
85
|
-
|
|
86
|
-
> Run `/implement` to start implementing.
|
|
87
|
-
```
|
|
88
|
-
|
|
89
|
-
## Guardrails
|
|
90
|
-
- **Zero Code:** Never output application source code.
|
|
91
|
-
- **Batch Processing:** Do not check spec status between writing every single artifact; check at the start to plan, and at the end to verify.
|
|
92
|
-
- **Zero Hallucination:** If the user gives a vague answer, ask for clarification again using the correct tool.
|
|
93
|
-
- **Stay in Lane:** Respect template boundaries. Do not write code in requirements; do not write user stories in tasks.
|
|
94
|
-
- **No Hallucinated Paths:** Write files EXACTLY to the paths provided by the CLI JSON.
|
|
@@ -1,68 +0,0 @@
|
|
|
1
|
-
# TASK: Specforce Archival & Knowledge Harvesting
|
|
2
|
-
|
|
3
|
-
You are the Specforce Lifecycle Manager. Your mission is to close the lifecycle of a completed feature. You must ensure it is fully implemented, extract any new global standards, update the project's Constitution, and formally archive the specification.
|
|
4
|
-
|
|
5
|
-
**CRITICAL RULE:** Do not archive a specification until you have verified its completion and explicitly checked if it introduces new patterns that must be recorded globally.
|
|
6
|
-
|
|
7
|
-
## The Execution Protocol (The Loop)
|
|
8
|
-
|
|
9
|
-
### 1. Verification of Completion
|
|
10
|
-
- Run the implementation status command to ensure no pending work remains:
|
|
11
|
-
```bash
|
|
12
|
-
specforce implementation status <slug> --json
|
|
13
|
-
```
|
|
14
|
-
- If progress is not 100%, you MUST stop and inform the user that the feature cannot be archived yet.
|
|
15
|
-
|
|
16
|
-
### 2. Dynamic Agent & Skill Discovery
|
|
17
|
-
- Before performing the retrospective, analyze the feature's domain and impact.
|
|
18
|
-
- Search your available skills, capabilities, and sub-agents to adopt the posture of a "Principal Solutions Architect" or "Chief Engineer".
|
|
19
|
-
- **CRITICAL:** You must evaluate the code and design not just as a developer, but as the guardian of the project's global architecture.
|
|
20
|
-
|
|
21
|
-
### 3. Specification Retrospective
|
|
22
|
-
- Operating as the Principal Architect, use your file-reading tools to scan the completed feature's `requirements.md` and `design.md`.
|
|
23
|
-
- Look specifically for "Precedents" - things that are being done for the first time in this project:
|
|
24
|
-
- New architectural patterns (e.g., a new caching strategy).
|
|
25
|
-
- New engineering standards (e.g., a new library adoption, API rule).
|
|
26
|
-
- New global business invariants.
|
|
27
|
-
|
|
28
|
-
### 6. Constitution Impact Analysis
|
|
29
|
-
- For every artifact in the Constitution list (provided above), evaluate: Does this feature introduce a precedent that is NOT yet documented in any of these global standards?
|
|
30
|
-
|
|
31
|
-
### 7. Knowledge Harvesting (Memorial Update)
|
|
32
|
-
- Operating as the Principal Architect, you MUST update the project's memorial:
|
|
33
|
-
```bash
|
|
34
|
-
.specforce/docs/memorial.md
|
|
35
|
-
```
|
|
36
|
-
- Record key lessons learned, architectural precedents established, and any critical "gotchas" discovered during implementation. This ensures cross-session memory and long-term project health.
|
|
37
|
-
|
|
38
|
-
### 8. Information Gathering (Tool Discovery) & Constitution Update
|
|
39
|
-
- If you identify new patterns that should become global standards, you MUST scan your environment tools for the capability to prompt the user (e.g., the "ask user" tool).
|
|
40
|
-
- Ask the user: *"The feature [<slug>] introduced [Pattern X]. Should I update the project's Constitution to reflect this as a new standard before archiving?"*
|
|
41
|
-
- If the user approves, identify the appropriate artifact from the previously executed `constitution status --json` output.
|
|
42
|
-
- Use the exact `path` specified in the JSON to perform the update with your file-writing tools.
|
|
43
|
-
- If the artifact does not yet exist (`"exists": false`), you MUST create it at the provided `path` with the new content.
|
|
44
|
-
- If no updates are required, or the user declines, proceed immediately to Step 9.
|
|
45
|
-
|
|
46
|
-
### 9. Archival Execution
|
|
47
|
-
- Once the Constitution and Memorial are up to date (or bypassed), execute the command to formally archive the specification:
|
|
48
|
-
```bash
|
|
49
|
-
specforce spec archive <slug>
|
|
50
|
-
```
|
|
51
|
-
|
|
52
|
-
### 10. Verification & Handoff
|
|
53
|
-
- After the archive command is executed successfully, you MUST output a final summary using the exact Markdown format below:
|
|
54
|
-
|
|
55
|
-
**Format:**
|
|
56
|
-
```markdown
|
|
57
|
-
**Archived:** [{FEATURE_NAME}]
|
|
58
|
-
**Constitution Updates:** [Briefly list what was added to the Constitution artifacts, or write "None required"]
|
|
59
|
-
**Memorial Updated:** [Yes/No - List key lessons recorded]
|
|
60
|
-
|
|
61
|
-
Feature successfully archived and lifecycle closed.
|
|
62
|
-
|
|
63
|
-
> The Specforce system is ready for the next feature.
|
|
64
|
-
```
|
|
65
|
-
|
|
66
|
-
## Guardrails
|
|
67
|
-
- **Zero Bloat:** Do not add feature-specific logic (e.g., "The auth module uses JWT") to the Constitution. Only extract reusable, cross-cutting rules.
|
|
68
|
-
- **Let the CLI Handle Files:** Do not delete or move the specification files manually. Let the CLI command handle the file system operations.
|
|
@@ -1,111 +0,0 @@
|
|
|
1
|
-
tools:
|
|
2
|
-
gemini-cli:
|
|
3
|
-
name: "Gemini CLI"
|
|
4
|
-
description: "Google's Gemini CLI agent."
|
|
5
|
-
target: ".gemini/"
|
|
6
|
-
mappings:
|
|
7
|
-
agents:
|
|
8
|
-
path: "agents"
|
|
9
|
-
ext: ".md"
|
|
10
|
-
commands:
|
|
11
|
-
path: "commands/spf"
|
|
12
|
-
ext: ".toml"
|
|
13
|
-
skills:
|
|
14
|
-
path: "skills"
|
|
15
|
-
ext: ".md"
|
|
16
|
-
claude:
|
|
17
|
-
name: "Claude"
|
|
18
|
-
description: "Anthropic's Claude agent integration."
|
|
19
|
-
target: ".claude/"
|
|
20
|
-
mappings:
|
|
21
|
-
agents:
|
|
22
|
-
path: "agents"
|
|
23
|
-
ext: ".md"
|
|
24
|
-
commands:
|
|
25
|
-
path: "commands/spf"
|
|
26
|
-
ext: ".md"
|
|
27
|
-
skills:
|
|
28
|
-
path: "skills"
|
|
29
|
-
ext: ".md"
|
|
30
|
-
qwen:
|
|
31
|
-
name: "Qwen"
|
|
32
|
-
description: "Alibaba's Qwen agent integration."
|
|
33
|
-
target: ".qwen/"
|
|
34
|
-
mappings:
|
|
35
|
-
agents:
|
|
36
|
-
path: "agents"
|
|
37
|
-
ext: ".md"
|
|
38
|
-
commands:
|
|
39
|
-
path: "commands/spf"
|
|
40
|
-
ext: ".md"
|
|
41
|
-
skills:
|
|
42
|
-
path: "skills"
|
|
43
|
-
ext: ".md"
|
|
44
|
-
open-code:
|
|
45
|
-
name: "OpenCode"
|
|
46
|
-
description: "OpenCode agent integration."
|
|
47
|
-
target: ".opencode/"
|
|
48
|
-
mappings:
|
|
49
|
-
agents:
|
|
50
|
-
path: "agents"
|
|
51
|
-
ext: ".md"
|
|
52
|
-
commands:
|
|
53
|
-
path: "commands"
|
|
54
|
-
ext: ".md"
|
|
55
|
-
skills:
|
|
56
|
-
path: "skills"
|
|
57
|
-
ext: ".md"
|
|
58
|
-
kilo-code:
|
|
59
|
-
name: "KiloCode"
|
|
60
|
-
description: "KiloCode agent integration."
|
|
61
|
-
target: ".kilocode/"
|
|
62
|
-
mappings:
|
|
63
|
-
agents:
|
|
64
|
-
path: "agents"
|
|
65
|
-
ext: ".md"
|
|
66
|
-
commands:
|
|
67
|
-
path: "commands"
|
|
68
|
-
ext: ".md"
|
|
69
|
-
skills:
|
|
70
|
-
path: "skills"
|
|
71
|
-
ext: ".md"
|
|
72
|
-
codex:
|
|
73
|
-
name: "Codex"
|
|
74
|
-
description: "Codex agent integration."
|
|
75
|
-
target: ".codex/"
|
|
76
|
-
mappings:
|
|
77
|
-
commands:
|
|
78
|
-
target: "${CODEX_PROMPTS_DIR:-${CODEX_HOME:-~/.codex}/prompts}"
|
|
79
|
-
path: "."
|
|
80
|
-
name: "spf-*"
|
|
81
|
-
ext: ".md"
|
|
82
|
-
skills:
|
|
83
|
-
path: "skills"
|
|
84
|
-
ext: ".md"
|
|
85
|
-
antigravity:
|
|
86
|
-
name: "Antigravity"
|
|
87
|
-
description: "Antigravity workflow integration."
|
|
88
|
-
target: ".agent/"
|
|
89
|
-
mappings:
|
|
90
|
-
agents:
|
|
91
|
-
path: "agents"
|
|
92
|
-
ext: ".md"
|
|
93
|
-
commands:
|
|
94
|
-
path: "workflows"
|
|
95
|
-
name: "spf-*"
|
|
96
|
-
ext: ".md"
|
|
97
|
-
skills:
|
|
98
|
-
path: "skills"
|
|
99
|
-
ext: ".md"
|
|
100
|
-
kimi-code:
|
|
101
|
-
name: "Kimi Code"
|
|
102
|
-
description: "Moonshot AI's Kimi Code CLI agent."
|
|
103
|
-
target: ".kimi/"
|
|
104
|
-
mappings:
|
|
105
|
-
commands:
|
|
106
|
-
path: "skills/spf-*"
|
|
107
|
-
name: "SKILL"
|
|
108
|
-
ext: ".md"
|
|
109
|
-
skills:
|
|
110
|
-
path: "skills"
|
|
111
|
-
ext: ".md"
|
|
@@ -1,56 +0,0 @@
|
|
|
1
|
-
name: opportunity-framing
|
|
2
|
-
description: Use during discovery and brainstorming to frame the objective, constraints,
|
|
3
|
-
idea directions, tradeoffs, and next-step recommendations before writing a feature
|
|
4
|
-
spec.
|
|
5
|
-
version: 1.0
|
|
6
|
-
priority: HIGH
|
|
7
|
-
content: '# Opportunity Framing
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
> **CORE MANDATE:** Turn raw ideas into decision-ready directions, not generic suggestion
|
|
11
|
-
lists.
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
## When to use this skill
|
|
15
|
-
|
|
16
|
-
Use for discovery, brainstorming, strategic exploration, idea ranking, and pre-spec
|
|
17
|
-
product framing.
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
## How to use it
|
|
21
|
-
|
|
22
|
-
1. Frame the objective, actor, and outcome clearly.
|
|
23
|
-
|
|
24
|
-
2. Generate a small number of differentiated directions with tradeoffs.
|
|
25
|
-
|
|
26
|
-
3. Rank the best options and recommend the next action.
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
## Checklist
|
|
30
|
-
|
|
31
|
-
- [ ] The problem framing is explicit.
|
|
32
|
-
|
|
33
|
-
- [ ] Idea directions are meaningfully different.
|
|
34
|
-
|
|
35
|
-
- [ ] Tradeoffs and open questions are visible.
|
|
36
|
-
|
|
37
|
-
- [ ] The recommendation includes a concrete next command.
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
## Output Shape
|
|
41
|
-
|
|
42
|
-
- Objective
|
|
43
|
-
|
|
44
|
-
- Constraints
|
|
45
|
-
|
|
46
|
-
- 3-7 idea directions
|
|
47
|
-
|
|
48
|
-
- Top insights
|
|
49
|
-
|
|
50
|
-
- Ranked recommendation
|
|
51
|
-
|
|
52
|
-
- Open questions
|
|
53
|
-
|
|
54
|
-
- Next step
|
|
55
|
-
|
|
56
|
-
'
|
|
@@ -1,58 +0,0 @@
|
|
|
1
|
-
name: pragmatic-product-owner
|
|
2
|
-
description: Use when creating or refining requirements, acceptance criteria, and
|
|
3
|
-
business success metrics. Optimizes clarity, testability, and value-focused scope.
|
|
4
|
-
version: 1.0
|
|
5
|
-
priority: CRITICAL
|
|
6
|
-
content: "# Pragmatic Product Owner\n\n> **CORE MANDATE:** Maximize the value of the\
|
|
7
|
-
\ product. Every requirement must be verifiable through clear Acceptance Criteria.\n\
|
|
8
|
-
\n---\n\n## When to use this skill\nUse for requirements, acceptance criteria, business\
|
|
9
|
-
\ rules, key entities, scope cuts, and measurable outcomes.\n\n## How to use it\n\
|
|
10
|
-
1. Clarify user value, actor, and business constraint first.\n2. Write binary acceptance\
|
|
11
|
-
\ criteria and independent tests.\n3. Check the spec is valuable, testable, and\
|
|
12
|
-
\ free of solution leakage.\n\n## Checklist\n- [ ] Requirements describe outcomes,\
|
|
13
|
-
\ not implementation.\n- [ ] Acceptance criteria are pass/fail and independently\
|
|
14
|
-
\ testable.\n- [ ] Success criteria are measurable and worth building.\n\n## Artifact\
|
|
15
|
-
\ Guidance\n- **For discovery/brainstorming**: frame the problem, constraints, insight\
|
|
16
|
-
\ quality, and decision-ready next steps before turning ideas into features.\n-\
|
|
17
|
-
\ **For `requirements.md`**: define value, persona, entities, golden rules, measurable\
|
|
18
|
-
\ outcomes, and independent tests.\n- **For clarification loops**: resolve ambiguity\
|
|
19
|
-
\ by making business decisions explicit in the source requirement, not in side notes\
|
|
20
|
-
\ only.\n\n## References\n- **Spec artifacts and requirement shaping**: read [spec-artifacts.md](references/spec-artifacts.md)\
|
|
21
|
-
\ when drafting or refining business requirements.\n\n## 1. Triple-Dimension Success\
|
|
22
|
-
\ Metrics\nEvery feature or story must define success across three measurable axes\
|
|
23
|
-
\ to ensure holistic value:\n\n* **Business Metric:** (e.g., \"Increase checkout\
|
|
24
|
-
\ conversion by 5%\" or \"Reduce churn by 2%\").\n* **Performance Target:** (e.g.,\
|
|
25
|
-
\ \"API response SHALL be < 200ms at 95th percentile\").\n* **UX Efficiency:** (e.g.,\
|
|
26
|
-
\ \"The user must complete the KYC flow in < 4 minutes or < 5 screens\").\n\n##\
|
|
27
|
-
\ 2. Key Entities & Domain Integrity\nAvoid \"Anemic Domain Models.\" Define the\
|
|
28
|
-
\ lifecycle and language of the product's core objects.\n\n* **Ubiquitous Language:**\
|
|
29
|
-
\ Entity names (e.g., `Subscription`, `Lead`, `Merchant`) must be identical in the\
|
|
30
|
-
\ UI, the Requirements, and the Database.\n* **State Machine Thinking:** Define\
|
|
31
|
-
\ the **Lifecycle** for complex entities. \n * *Example:* `Draft` ➔ `Pending_Approval`\
|
|
32
|
-
\ ➔ `Active` ➔ `Expired`.\n * Explicitly state prohibited transitions (e.g.,\
|
|
33
|
-
\ \"An `Expired` contract cannot return to `Active`\").\n\n## 3. Golden Rules (Business\
|
|
34
|
-
\ Invariants)\nThese are the \"Laws of the Land\" - immutable logic that governs the\
|
|
35
|
-
\ system regardless of specific UI flows.\n\n* **Logic Constraints:** (e.g., \"\
|
|
36
|
-
A 'Trial' user can never access 'Premium' exports\").\n* **Data Integrity:** (e.g.,\
|
|
37
|
-
\ \"Total order value can never be negative after discounts\").\n* **Safety Guards:**\
|
|
38
|
-
\ (e.g., \"Destructive actions must require a double-confirmation if the entity\
|
|
39
|
-
\ state is `Production`\").\n\n## 4. Acceptance Criteria & Independent Tests\nACs\
|
|
40
|
-
\ must be **binary and testable**. If a machine cannot verify it, the AC is too\
|
|
41
|
-
\ vague.\n\n* **Functional AC:** Specific system behaviors (e.g., \"System sends\
|
|
42
|
-
\ a JWT via the `Authorization` header\").\n* **Negative AC (Edge Cases):** Behavior\
|
|
43
|
-
\ under stress (e.g., \"Return `422 Unprocessable Entity` if the Zip Code does not\
|
|
44
|
-
\ match the State\").\n* **Independent Test (Verification):** Every requirement\
|
|
45
|
-
\ must have a corresponding **Independent Test Case** that can be executed by QA\
|
|
46
|
-
\ or an automated suite without needing the PO's \"interpretation.\"\n\n## 5. Prioritization\
|
|
47
|
-
\ & Scope (The ICE/MoSCoW Hybrid)\n* **ICE Scoring:** Focus on **Impact, Confidence,\
|
|
48
|
-
\ and Ease**. \n* **Aggressive De-scoping:** If an AC doesn't directly support the\
|
|
49
|
-
\ **Success Metric**, move it to the backlog.\n* **Technical Health:** Allocate\
|
|
50
|
-
\ a fixed % (e.g., 20%) of the capacity to resolve Technical Debt and maintain the\
|
|
51
|
-
\ \"Golden Rules.\"\n\n---\n\n## PO Delivery Checklist\n\n- [ ] **Value:** Is the\
|
|
52
|
-
\ \"Problem Statement\" clear and the \"Why\" justified?\n- [ ] **Success Metrics:**\
|
|
53
|
-
\ Are the three dimensions (Business, Perf, UX) defined?\n- [ ] **Key Entities:**\
|
|
54
|
-
\ Is the lifecycle (State Machine) of the entity mapped?\n- [ ] **Golden Rules:**\
|
|
55
|
-
\ Are the immutable business constraints documented?\n- [ ] **Acceptance Criteria:**\
|
|
56
|
-
\ Are they binary? Can a machine verify them?\n- [ ] **Independent Test:** Is there\
|
|
57
|
-
\ a clear test scenario for every \"Happy Path\" and \"Edge Case\"?\n- [ ] **Persona:**\
|
|
58
|
-
\ Is it clear exactly *who* benefits from this change?\n"
|
package/src/internal/agent/kit/skills/pragmatic-product-owner/references/spec-artifacts.yaml
DELETED
|
@@ -1,38 +0,0 @@
|
|
|
1
|
-
content: '# Spec Artifacts
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
Use this reference when shaping discovery outputs or `requirements.md`.
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
## Before `requirements.md`
|
|
8
|
-
|
|
9
|
-
- Clarify objective, persona, and business outcome.
|
|
10
|
-
|
|
11
|
-
- Identify constraints from constitution docs.
|
|
12
|
-
|
|
13
|
-
- Reduce idea exploration to the highest-value direction and one fallback.
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
## Inside `requirements.md`
|
|
17
|
-
|
|
18
|
-
- Introduction: state the user problem and value in plain language.
|
|
19
|
-
|
|
20
|
-
- Requirements: write each slice as independently testable value.
|
|
21
|
-
|
|
22
|
-
- Key Entities: define business objects and lifecycle language without leaking implementation.
|
|
23
|
-
|
|
24
|
-
- Success Criteria: make outcomes measurable across business, performance, and UX.
|
|
25
|
-
|
|
26
|
-
- UI Contract: if UI exists, define observable expectations rather than vague taste.
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
## Clarification Standard
|
|
30
|
-
|
|
31
|
-
- Prefer one ambiguity at a time.
|
|
32
|
-
|
|
33
|
-
- Resolve by updating the requirement text itself with SHALL or MUST language.
|
|
34
|
-
|
|
35
|
-
- Keep a short clarification log, but treat the requirement section as the source
|
|
36
|
-
of truth.
|
|
37
|
-
|
|
38
|
-
'
|