superwiki 0.1.1 → 0.1.3

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.
@@ -20,8 +20,8 @@ Needs the task module (`docs/tasks/`). If it is missing, say so and offer sw-ini
20
20
  4. **Dispatch the planner.** Its prompt is: the task id, today's date, the project root if it is not your working directory, and any feedback from an earlier round. It writes the plan file as a draft and returns a short message.
21
21
 
22
22
  | Tool | How |
23
- |---|---|
24
- | Claude Code | agent `sw-planner`. If it is not among your agent types, use a general-purpose agent, put the content of `<skill-dir>/../sw-config/assets/planner.md` at the top of its prompt, and pass the model from `models.plan.claude` in `docs/.sw/config.json` if set |
23
+ | --- | --- |
24
+ | Claude Code | agent `sw-planner`. If it is not among your agent types, use a general-purpose agent, tell it to read `<skill-dir>/../sw-config/assets/planner.md` first and follow it, and pass the model from `models.plan.claude` in `docs/.sw/config.json` if set |
25
25
  | Codex | spawn the custom agent `sw_planner` |
26
26
  | Copilot CLI | `task` tool with agent `sw-planner` |
27
27
  | No subagents available, or the agent is not defined | follow `planner.md` yourself, in this session, and tell the user the configured model was not used |
@@ -32,9 +32,9 @@ Needs the task module (`docs/tasks/`). If it is missing, say so and offer sw-ini
32
32
  - The user drops the plan: delete the draft file.
33
33
  6. **Record**, after approval:
34
34
  - in the plan file, change `status: draft` to `status: approved`;
35
- - answers given in step 5: add to the task's "Notes";
36
- - the planner's `Guide:` lines: add to the area guide (see sw-implement, "Keep the area guide");
37
- - `docs/log.md`: append `## [date] plan | <ID>`, in the layout the log's last entries use.
35
+ - in the task's "Notes", the answers given in step 5;
36
+ - in the area guide, if `node docs/.sw/sw.mjs explain <ID>` names one, the planner's `Guide:` lines, one line per fact;
37
+ - in `docs/log.md`, a new entry `## [date] plan | <ID>`, in the layout the log's last entries use.
38
38
 
39
39
  Then run `node docs/.sw/sw.mjs lint`.
40
40
  7. **Stop.** Do not start implementing. Tell the user the plan is approved and that sw-implement `<ID>` runs it.