Merge pull request #17 from unic/develop

Develop

Author: orioltf

.claude/commands/inbox.md

@@ -0,0 +1,66 @@
+---
+allowed-tools: [Write, Bash]
+argument-hint: '<one-liner idea>'
+description: 'Capture a raw idea into docs/inbox/ without interrupting the current conversation'
+---
+
+# Inbox capture
+
+**Arguments:** "$ARGUMENTS"
+
+Capture the idea in `$ARGUMENTS` as a file in `docs/inbox/`. Act immediately — no follow-up
+questions.
+
+## Step 1 — Generate a slug
+
+From the idea text:
+
+1. Lowercase everything
+2. Replace spaces and punctuation with hyphens
+3. Collapse multiple hyphens into one
+4. Strip leading/trailing hyphens
+5. Truncate to 50 characters at a word boundary
+
+Examples:
+
+- `"pr-review should support GitLab!"` → `pr-review-should-support-gitlab`
+- `"add dark mode support to the dashboard component"` → `add-dark-mode-support-to-the-dashboard-component`
+- `"implement user authentication with OAuth2 and role-based access control"` → `implement-user-authentication-with-oauth2-and` (truncated at word boundary before 50 chars)
+
+## Step 2 — Check for collisions
+
+```bash
+node -e "
+  const root = require('child_process').execSync('git rev-parse --show-toplevel').toString().trim();
+  const p = require('path').join(root, 'docs', 'inbox', '<slug>.md');
+  process.exit(require('fs').existsSync(p) ? 0 : 1);
+"
+```
+
+If the file exists, append `-2` (then `-3`, etc.) until the path is free.
+
+## Step 3 — Write the file
+
+Resolve the repo root with `git rev-parse --show-toplevel`, then create `<root>/docs/inbox/<slug>.md`:
+
+```markdown
+---
+title: <original idea text, trimmed>
+created: <today's date as YYYY-MM-DD>
+---
+
+<original idea text, trimmed>
+```
+
+Use the `Write` tool. Do not create any other files.
+
+## Step 4 — Confirm
+
+Reply with exactly one line:
+
+```txt
+Captured → docs/inbox/<slug>.md
+```
+
+Nothing else. No summary, no next steps, no follow-up questions. The user is in the middle
+of something else.

.claude/skills/verify-spec/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: verify-spec
 description: This skill should be used when the user asks to "verify spec 15", "check acceptance criteria for spec N", "is spec 14 ready to merge", "run verify-spec on 08", "check if spec 15 is done", or invokes /verify-spec with a spec number or filename. Locates the matching spec file and checks every acceptance criterion against the current codebase.
-argument-hint: "<spec-number-or-filename> (e.g. 15 or 15-release-tools-tests.md)"
+argument-hint: '<spec-number-or-filename> (e.g. 15 or 15-release-tools-tests.md)'
 user-invocable: true
 ---
 

.idea/codeStyles/Project.xml

@@ -20,7 +20,7 @@ packages/
 ├── tsconfig/                 # @unic/tsconfig
 └── release-tools/            # @unic/release-tools (bump / sync-version / tag / verify-changelog)
 docs/
-└── plans/                    # Monorepo-level Ralph spec roadmap (specs 00–14)
+└── plans/                    # Monorepo-level Spec Runner roadmap (specs 00–14)
 ```
 
 Each plugin under `apps/<agent>/` also has its own `docs/plans/` for plugin-specific future work.
@@ -41,12 +41,12 @@ pnpm format                             # Biome + Prettier fix (whole tree)
 pnpm ci:check                           # same as check, non-interactive (for CI)
 pnpm test                               # run tests across all packages
 pnpm typecheck                          # type-check across all packages
-pnpm ralph                              # run the monorepo Ralph loop (specs 00–14)
+pnpm ralph                              # run the monorepo Spec Runner loop (specs 00–14)
 
 # Per-plugin operations (after spec 03 sets up release-tools)
 pnpm --filter <name> bump patch         # bump plugin version
 pnpm --filter <name> verify:changelog   # check changelog
-pnpm --filter <name> ralph              # run that plugin's own Ralph loop
+pnpm --filter <name> ralph              # run that plugin's own Spec Runner loop
 ```
 
 ## Tech stack
@@ -126,7 +126,7 @@ All work starts with a spec file under `docs/plans/`. Specs follow this format:
 ## Out of scope
 ```
 
-`pnpm ralph` runs Ralph Orchestrator, which implements specs one at a time in a loop.
+`pnpm ralph` runs the Spec Runner (currently `ralph-orchestrator`), which implements specs one at a time in a loop.
 
 ## Do not add
 
@@ -150,4 +150,8 @@ Issues live as local markdown files under `docs/issues/`. See `docs/agents/issue
 
 ### Domain docs
 
-Multi-context repo: Per-plugin `CONTEXT.md` files (created lazily by `/grill-with-docs`) live under `apps/claude-code/<plugin>/`. A root `CONTEXT-MAP.md` may be added later. See `docs/agents/domain.md`.
+Multi-context repo: Per-plugin `CONTEXT.md` files live under `apps/claude-code/<plugin>/`. Root `CONTEXT-MAP.md` at repo root. See `docs/agents/domain.md`.
+
+### Inbox
+
+Raw ideas, bugs, and stray thoughts that haven't been grilled or scoped yet live in `docs/inbox/`. Use `/inbox <one-liner>` to capture without interrupting the current flow. Items graduate to `docs/issues/<slug>/` after grilling. See `docs/inbox/README.md`.