@domain-first/project-structure 8.10.0 → 8.10.1
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/package.json
CHANGED
|
@@ -5,7 +5,7 @@ description: Turn an abstract feature request into a Domain-First plan for a pro
|
|
|
5
5
|
|
|
6
6
|
# Plan a feature
|
|
7
7
|
|
|
8
|
-
Understand → decompose → assign → get approval → hand off. A feature creates files, so nothing is generated or written before approval (`df-ps-scaffold`, rule 1).
|
|
8
|
+
Understand → decompose → assign → get approval → hand off. A feature creates files, so nothing is generated or written before approval (`df-ps-scaffold`, rule 1). This step is removed only when the user explicitly says that no plan is needed: the message names the plan itself and declines it ("skip the plan", "without a plan", "no plan needed"), in whatever language the user writes. A request that doesn't mention the plan ("let's build the order export", "just do it") is always a request to write the plan, however direct or urgent it sounds.
|
|
9
9
|
|
|
10
10
|
## 1. Understand what exists
|
|
11
11
|
|
|
@@ -23,13 +23,13 @@ Follow this order for every request:
|
|
|
23
23
|
|
|
24
24
|
### 1. Work plan approval
|
|
25
25
|
|
|
26
|
-
**A task that creates any new file** (a df-scaffold run, or a hand-created file under rule 2) needs an approved work plan first, even for one component. The plan can be skipped only when the user
|
|
26
|
+
**A task that creates any new file** (a df-scaffold run, or a hand-created file under rule 2) needs an approved work plan first, even for one component. The plan can be skipped only when the user explicitly says, for this task, that no plan is needed: the message names the plan itself and declines it ("skip the plan", "without a plan", "no plan needed"), in whatever language the user writes. A request that doesn't mention the plan always starts with one, however direct or urgent it sounds ("let's build the order export", "just do it", "build it now", "no need to ask"). Never infer that the user wants no plan from the size of the task, its urgency or earlier tasks. This is about skipping the plan: once a plan is shown, an ordinary "yes" or "go ahead" approves it. Until approval, only read (`--describe` and `dryRun: true` do not write files). Files written by the project's own scripts (rule 2, exception 2) don't count: run those scripts when the work needs them.
|
|
27
27
|
|
|
28
28
|
Tasks that only edit existing files (a bug fix, a new field, a changed rule) don't need a plan: do them directly and say what you changed.
|
|
29
29
|
|
|
30
30
|
Read [references/work-plan.md](references/work-plan.md), show the plan in that format and stop.
|
|
31
31
|
|
|
32
|
-
- Approval must be explicit ("ok", "
|
|
32
|
+
- Approval must be explicit ("ok", "yes", "go ahead"…). A question or silence isn't approval. Changes to the plan → show the updated plan and ask again.
|
|
33
33
|
- After approval, do exactly the plan. An extra module or file, or a different name/option → stop and get the delta approved. Edits to existing files needed along the way don't need approval; list them in the final report.
|
|
34
34
|
|
|
35
35
|
### 2. New files only through df-scaffold
|