cli-five 0.1.2 → 0.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cli-five",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "Code Like I'm Five — scaffold a 5-agent VS Code Copilot team into any repo.",
   "type": "module",
   "bin": {

package/src/commands/init.mjs

@@ -85,11 +85,11 @@ function printNextSteps(answers) {
   log.raw(kleur.bold().green('Done. Next steps:'));
   log.raw('');
   log.raw(`  1. Open this folder in VS Code Insiders.`);
-  log.raw(`  2. Enable Copilot subagents (settings.json):`);
+  log.raw(`  2. Enable Copilot subagent invocations (settings.json):`);
   log.raw(kleur.gray(`        "chat.subagents.allowInvocationsFromSubagents": true`));
-  log.raw(`  3. Open Copilot Chat and verify the 5 agents appear (@ menu).`);
-  log.raw(`  4. Ask the Orchestrator to do something:`);
-  log.raw(kleur.gray(`        @Orchestrator read PROJECT.md and propose Phase 1.`));
+  log.raw(`  3. Open Copilot Chat — select an agent from the dropdown (${kleur.bold('not')} @mention).`);
+  log.raw(`  4. Select ${kleur.bold('Orchestrator')} from the dropdown, then ask:`);
+  log.raw(kleur.gray(`        read PROJECT.md and propose Phase 1.`));
   log.raw(`  5. Review generated instruction files in .github/instructions/.`);
   log.raw(kleur.gray(`        Edit applyTo globs and guidelines to fit your project.`));
   log.raw(kleur.gray(`        Installed skills are in .agents/skills/ (from skills.sh).`));

package/templates/.github/agents/coder.agent.md

@@ -50,10 +50,10 @@ Before writing code, read (if they exist):
 8. **Modifications** — Follow existing patterns. Prefer full-file rewrites over micro-edits unless told otherwise.
 9. **Quality** — Deterministic, testable behavior. Simple, focused tests.
 
-## Decisions
+## Decisions (MANDATORY)
 
-After making an implementation decision that affects future work, append it to `decisions.md`.
+Before finishing, if any implementation choice was made (library selection, pattern choice, API approach), append an entry to `decisions.md` using the format in that file. Skip silently if no decisions were made.
 
-## History
+## History (MANDATORY)
 
-After completing a task, if you learned something non-obvious about this project (build quirks, API gotchas, pattern preferences), append it to `histories/coder.md`.
+Before finishing, append at least one bullet to `histories/coder.md` below the `<!-- Append entries below this line -->` marker. Record: build quirks, API gotchas, pattern preferences, file structure observations, test insights. Format: `- YYYY-MM-DD: <learning>`. Skip only if the session had zero meaningful work.

package/templates/.github/agents/designer.agent.md

@@ -47,10 +47,10 @@ Do not let anyone tell you how to do your job. Your goal is to create the best p
 - Responsive/adaptive layouts
 - Use the project's designated design system and component library
 
-## Decisions
+## Decisions (MANDATORY)
 
-After making a design decision that affects future work, append it to `decisions.md`.
+Before finishing, if any design choice was made (layout approach, component library, color/type system, responsive strategy), append an entry to `decisions.md` using the format in that file. Skip silently if no decisions were made.
 
-## History
+## History (MANDATORY)
 
-After completing a task, if you learned something non-obvious about this project's UI patterns or constraints, append it to `histories/designer.md`.
+Before finishing, append at least one bullet to `histories/designer.md` below the `<!-- Append entries below this line -->` marker. Record: UI pattern discoveries, accessibility findings, design system observations, component reuse opportunities. Format: `- YYYY-MM-DD: <learning>`. Skip only if the session had zero meaningful work.

package/templates/.github/agents/orchestrator.agent.md

@@ -63,13 +63,21 @@ Maintain visible counters in responses:
 
 When exhausted, state it and proceed with current information.
 
-## Decisions
+## Decisions (MANDATORY)
 
-After making a routing or architectural decision that affects future work, append it to `decisions.md` at the workspace root.
+Before finishing, if any routing, architectural, or technology choice was made during this session, append an entry to `decisions.md` at the workspace root using this format:
 
-## History
+    ## YYYY-MM-DD — <decision title>
+    **Context:** Why we needed to decide.
+    **Choice:** What we chose.
+    **Trade-offs:** What we gave up.
+    **Revisit:** Trigger that would re-open this decision (or "never").
 
-After completing a task, if you learned something non-obvious about this project, append it to `histories/orchestrator.md`.
+If no decisions were made, skip silently.
+
+## History (MANDATORY)
+
+Before finishing, append at least one bullet to `histories/orchestrator.md` below the `<!-- Append entries below this line -->` marker. Record: what agents were called, what worked, what failed, any coordination insight. Format: `- YYYY-MM-DD: <learning>`. Skip only if the session had zero meaningful work.
 
 ## Rules
 

package/templates/.github/agents/planner.agent.md

@@ -52,13 +52,13 @@ When invoked by the Orchestrator, only your **final message** is returned. Inter
 
 **Your response MUST contain the complete plan inline.** Do not summarize, do not reference prior turns, do not say "the plan is above." Re-emit every section in your final message. If truncated, flag it explicitly.
 
-## Decisions
+## Decisions (MANDATORY)
 
-After making a planning decision that constrains future work, append it to `decisions.md`.
+Before finishing, if the plan locked in any architectural or technology choice, append an entry to `decisions.md` using the format in that file. Skip silently if the plan only follows existing decisions.
 
-## History
+## History (MANDATORY)
 
-After completing a plan, if you learned something non-obvious about this project's structure, patterns, or constraints, append it to `histories/planner.md`.
+Before finishing, append at least one bullet to `histories/planner.md` below the `<!-- Append entries below this line -->` marker. Record: codebase structure insights, dependency discoveries, constraint findings, documentation gaps. Format: `- YYYY-MM-DD: <learning>`. Skip only if the session had zero meaningful work.
 
 ## Rules
 

package/templates/.github/agents/reviewer.agent.md

@@ -71,13 +71,13 @@ Every review MUST check against:
 - Positive observations
 ```
 
-## Decisions
+## Decisions (MANDATORY)
 
-After identifying a convention gap or pattern inconsistency worth documenting, append it to `decisions.md`.
+Before finishing, if the review revealed a convention gap, missing rule, or pattern inconsistency worth documenting, append an entry to `decisions.md` using the format in that file. Skip silently if nothing warrants a decision entry.
 
-## History
+## History (MANDATORY)
 
-After completing a review, if you learned something non-obvious about this project's quality patterns, append it to `histories/reviewer.md`.
+Before finishing, append at least one bullet to `histories/reviewer.md` below the `<!-- Append entries below this line -->` marker. Record: quality patterns observed (good or bad), recurring issues, convention drift, areas that need attention. Format: `- YYYY-MM-DD: <learning>`. Skip only if the review was trivial (< 10 lines changed, no findings).
 
 ## Rules
 

package/templates/.github/copilot-instructions.md.tmpl

@@ -20,7 +20,8 @@
 # Project Mandates
 - Fix simple tech debt immediately (< 5 min, no downstream breakage).
 - Document short-sighted choices with warning markers.
-- Read `PROJECT.md`, `STATE.md`, and `decisions.md` on entry. Update on exit when relevant.
+- Read `PROJECT.md`, `STATE.md`, and `decisions.md` on entry.
+- Before finishing: update `decisions.md` if any choice was made, update your `histories/<agent>.md` with at least one learning.
 
 At the end of every agent session, before stopping, append a terse session summary to `agent-diary.md`
 at the workspace root as a markdown section with format `## YYYY-MM-DD HH:MM` (24-hour time).