nikos 0.0.4 → 0.0.5

package/dist/commands/decide.js

@@ -2,7 +2,7 @@ import { appendFileSync, existsSync } from "node:fs";
 import { join } from "node:path";
 import { STORY_ID, findIntentDir, read } from "../lib/project.js";
 import { formatResult, validate } from "./validate.js";
-const CATEGORIES = ["product", "architecture", "design", "process"];
+const CATEGORIES = ["product", "architecture", "design", "interface", "process"];
 /** Append a dated entry to decisions.md. Earlier entries are never touched. */
 export function decide(input, dir) {
     const title = input.title.trim();
@@ -39,7 +39,7 @@ export function runDecide(args) {
         return i >= 0 ? rest[i + 1] : undefined;
     };
     if (!title || title.startsWith("--")) {
-        console.error('Usage: nikos decide "<title>" --why "<why>" [--story <id>] [--category product|architecture|design|process] [--supersedes "<title>"]');
+        console.error('Usage: nikos decide "<title>" --why "<why>" [--story <id>] [--category product|architecture|design|interface|process] [--supersedes "<title>"]');
         return 1;
     }
     const dir = opt("dir") ?? process.cwd();

package/docs/format.md

@@ -199,7 +199,9 @@ Why this, and what we rejected.
 
 The heading is `date — title (story id)`; the story id is optional for
 project-wide decisions. Category is one of `product`, `architecture`,
-`design`, `process`.
+`design`, `interface`, `process`. Use `interface` for a choice other stories
+must keep to: a command's syntax, an output format, an API's shape. The
+build-a-story playbook reads these before planning.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nikos",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "Spec-driven development for AI coding agents: story maps, Gherkin acceptance criteria and a done gate for Claude Code, Codex and Cursor",
   "license": "MIT",
   "author": "Niko Vijay",

package/skills/clear/SKILL.md

@@ -31,9 +31,23 @@ Read the story's `.feature` file, `intent/constitution.md` and
 - **Accurate:** it agrees with the constitution (who it's for, the problem,
   the proof) and with every decision in `decisions.md`. Name the line it
   contradicts.
-- **Responsible:** where the story touches personal data, money, safety,
-  outreach to real people or accessibility, a scenario or the description
-  covers it. A story that touches none of these passes and says so.
+- **Responsible:** for each area below that the story touches, every item
+  in its row is covered by a scenario (or, where the row says so, stated in
+  the description). Any missing item fails Responsible: name the item and give
+  the scenario to add. A story that touches none of these areas passes and
+  says so.
+
+  | Area | The story must cover |
+  | --- | --- |
+  | Money | A scenario for invalid amounts (zero, negative, more decimals than the currency has); a scenario for how amounts round; the currency, in the description or a scenario |
+  | Personal data | Who can see it, in the description or a scenario; a scenario for deleting it |
+  | Safety (health, physical harm, locks, children) | A scenario for what happens when it fails, and what the user sees then |
+  | Outreach to real people | A scenario for consent or opting out; nothing is sent without the person's sign-off |
+  | A screen people use | A scenario or description line saying it works by keyboard and with a screen reader |
+
+  For example, a story that charges a card but has no scenario for a zero or
+  negative amount reports:
+  `Responsible: fail. Money: no scenario for invalid amounts. Fix: add "AC3 — A zero or negative amount is refused".`
 
 ## 3. Fill small gaps, ask about big ones
 

package/skills/decisions/SKILL.md

@@ -38,7 +38,7 @@ add what the git history of `intent/` shows (`git log -p -- intent/`), marked
 clearly as history, not a recorded decision. Then offer to log one:
 
 ```
-nikos decide "<title>" --why "<why>" --category <product|architecture|design|process>
+nikos decide "<title>" --why "<why>" --category <product|architecture|design|interface|process>
 ```
 
 Log it only once the person tells you the reason. Don't write a reason for

package/skills/nikos-mode/playbooks/build-a-story.md

@@ -5,10 +5,10 @@ scenarios pass, not that you say so.
 
 1. Run `nikos next` to pick the story, or use the story id the person named.
 2. Check the story with the clear skill, and stop if any of the five checks fails.
-3. Run `nikos plan new <story-id>` and write the approach into the plan file it creates.
-4. Run `nikos state set <story-id> in_progress`.
+3. Run `nikos decisions interface`, then `nikos plan new <story-id>` and write the approach into the plan file it creates. Reuse every interface decision the story touches, and cite each in the step that uses it as `Reuses: <decision title> (intent/decisions.md:<lines>)`. If the story needs to change one, stop and ask.
+4. Run `nikos state set <story-id> in_progress --by <agent>`, where `<agent>` names your tool (`claude-code`, `codex`, `cursor`), never a person, so `state.yaml` shows who is building it.
 5. Implement the story, with a step definition for each step in its scenarios (see the verify skill).
 6. Run `nikos verify <story-id>`, then `nikos verify` to check every other story still passes, and keep the output.
-7. Record each decision you made with `nikos decide "<title>" --story <story-id> --why "<why>"`.
+7. Record each decision you made with `nikos decide "<title>" --story <story-id> --why "<why>"`. Add `--category interface` for anything a later story must keep to: command syntax, output format, API shape.
 8. Run `nikos state set <story-id> done`. If it refuses, fix the failing scenarios and go back to step 6.
 9. Report every step with its evidence or its skip reason.

package/templates/intent/decisions.md

@@ -5,7 +5,7 @@ one that supersedes it.
 
 <!--
 ## YYYY-MM-DD — Decision title (STORY-ID)
-**Category:** product | architecture | design | process
+**Category:** product | architecture | design | interface | process
 **Supersedes:** none
 
 Why this, and what we rejected.