aligndev 0.20.1 → 0.20.2
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 +1 -1
- package/templates/guide/code.md +6 -4
package/package.json
CHANGED
package/templates/guide/code.md
CHANGED
|
@@ -236,15 +236,17 @@ Prefer `--message-file` for long or multi-line messages. A quoted heredoc delimi
|
|
|
236
236
|
|
|
237
237
|
## Answering the agent's questions
|
|
238
238
|
|
|
239
|
-
During spec and AAD sessions the agent asks questions
|
|
239
|
+
During spec and AAD sessions the agent asks numbered questions, `Q1`, `Q2`…, each with a ➡️ recommendation. Resume **without a protocol** to answer. Compose the answers in English, all in one message, numbered to match:
|
|
240
240
|
|
|
241
241
|
```bash
|
|
242
242
|
{{ALIGNDEV}} code resume <sessionId> --message \
|
|
243
|
-
"
|
|
244
|
-
|
|
245
|
-
|
|
243
|
+
"Q1 - Explore the codebase and give me your opinion.
|
|
244
|
+
Q2 - Is that a good design? We need the cleanest code possible.
|
|
245
|
+
Q3 - Yes, it should be optional."
|
|
246
246
|
```
|
|
247
247
|
|
|
248
|
+
A question your reply skips stays open. Accept a whole round only once your user has settled every decision that is theirs: "All recommendations accepted, except Q3: <what to do instead>."
|
|
249
|
+
|
|
248
250
|
**Technical questions** — architecture, patterns, existing behavior, anything answerable by reading the code. Never escalate these to the user. Push the agent to investigate: *"Explore the codebase to find out, and give me your opinion."*, *"Do not rush. Take the time to fully understand the situation first."*, *"What would be the elegant, proper, simple yet robust solution?"*, *"Check if a similar pattern is already implemented elsewhere in the codebase."*
|
|
249
251
|
|
|
250
252
|
**Functional or UX questions** — product behavior, user-facing decisions, business rules. These need human judgement: escalate to your user, then relay the answer.
|