nikos 0.0.3 → 0.0.4

package/README.md

@@ -4,6 +4,15 @@
 
 <p align="center"><b>Spec-driven development for AI coding agents</b></p>
 
+I'm [@nikovijay](https://x.com/nikovijay), a Product Director with 20 years
+of experience in software delivery. nikOS is my personal framework for
+building products with AI coding agents. I'm sharing it to help others get
+started with agentic programming practices. For where I think this is going,
+see my thoughts on
+[the software factory of the near future](https://www.nikovijay.com/software-factory).
+
+## What it does
+
 AI coding agents are quick to say "done". nikOS makes them prove it. Your
 story map, plans and acceptance criteria live in your repo as plain files,
 each criterion is a Cucumber scenario that runs as a test, and a story can't
@@ -11,6 +20,10 @@ be marked done until its scenarios pass. Your agent follows a named playbook
 for each request instead of improvising, and every decision is written down
 where the next person (or agent) can find it.
 
+It works with Claude Code, Codex and Cursor, and brings spec-driven
+development, behaviour-driven development (BDD) with Gherkin and Cucumber,
+user story mapping and acceptance criteria to agentic coding.
+
 > Early work in progress. Open source, MIT licensed.
 
 ## Try it in 10 minutes
@@ -80,20 +93,6 @@ Every file is plain text you can read, review and diff. The full format:
 | `nikos decisions "<q>"` | Quote the decisions about a topic or story |
 | `nikos bet new <id>` | Write a time-boxed bet card linked to its stories |
 
-## Working with a team: intentdocs
-
-When you want a visual story map, reviews and a team around the same specs,
-[intentdocs](https://www.intentdocs.com) reads the same `intent/` folder:
-
-```bash
-npx intentdocs push    # upload intent/ and link this repo
-npx intentdocs pull    # bring web edits back, shown as diffs first
-```
-
-The repo stays the source of truth for specs and plans; intentdocs runs the
-build and acceptance steps. What maps to what:
-[docs/intentdocs-mapping.md](docs/intentdocs-mapping.md).
-
 ## Links
 
 - Home: https://nikos.tools

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", "interface", "process"];
+const CATEGORIES = ["product", "architecture", "design", "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|interface|process] [--supersedes "<title>"]');
+        console.error('Usage: nikos decide "<title>" --why "<why>" [--story <id>] [--category product|architecture|design|process] [--supersedes "<title>"]');
         return 1;
     }
     const dir = opt("dir") ?? process.cwd();

package/docs/format.md

@@ -199,9 +199,7 @@ 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`, `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.
+`design`, `process`.
 
 ---
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "nikos",
-  "version": "0.0.3",
-  "description": "nikOS \u2014 an open-source agent skill stack for spec-driven development. Specs, plans and Cucumber features live in your repo.",
+  "version": "0.0.4",
+  "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",
   "homepage": "https://nikos.tools",
@@ -42,5 +42,19 @@
     "@cucumber/messages": "^26.0.1",
     "ajv": "^8.17.1",
     "yaml": "^2.6.1"
-  }
+  },
+  "keywords": [
+    "spec-driven-development",
+    "ai-coding-agents",
+    "agentic-coding",
+    "claude-code",
+    "codex",
+    "cursor",
+    "bdd",
+    "gherkin",
+    "cucumber",
+    "acceptance-criteria",
+    "user-story-mapping",
+    "agent-skills"
+  ]
 }

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|interface|process>
+nikos decide "<title>" --why "<why>" --category <product|architecture|design|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 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.
+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`.
 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>"`. Add `--category interface` for anything a later story must keep to: command syntax, output format, API shape.
+7. Record each decision you made with `nikos decide "<title>" --story <story-id> --why "<why>"`.
 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 | interface | process
+**Category:** product | architecture | design | process
 **Supersedes:** none
 
 Why this, and what we rejected.