@orderful/droid 0.26.0 → 0.27.0

package/src/tools/codex/skills/{droid-codex → codex}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: droid-codex
+name: codex
 description: "Shared organizational knowledge - PRDs, tech designs, patterns, and explored topics. Use when loading project context ('load transaction-templates'), searching codex ('search webhook'), capturing decisions ('codex decision'), or adding explored topics ('add topic'). User prompts like 'check the codex', 'what's in the codex about X', 'load the PRD for Y'."
 globs:
   - "**/PRD.md"
@@ -7,7 +7,18 @@ globs:
   - "**/CONTEXT.md"
   - "**/DECISIONS.md"
 alwaysApply: false
-allowed-tools: [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(ls:*), Bash(mkdir:*)]
+allowed-tools:
+  [
+    Read,
+    Write,
+    Edit,
+    Glob,
+    Grep,
+    Bash(gh:*),
+    Bash(git:*),
+    Bash(ls:*),
+    Bash(mkdir:*),
+  ]
 ---
 
 # Codex Skill
@@ -32,6 +43,7 @@ gh --version
 ```
 
 If prerequisites fail, guide user to fix:
+
 - Repo missing: `git clone git@github.com:orderful/orderful-codex.git {path}`
 - gh missing: `brew install gh && gh auth login`
 
@@ -43,16 +55,16 @@ If prerequisites fail, guide user to fix:
 
 The codex skill includes three git scripts. **Always use these instead of raw git commands.**
 
-| Script | Purpose | When to use |
-|--------|---------|-------------|
-| `git-preamble` | Ensure clean main + pull latest | Before ANY operation |
-| `git-start-write` | Preamble + create branch | Before write operations |
-| `git-finish-write` | Commit + PR + return to main | After write operations |
+| Script             | Purpose                         | When to use             |
+| ------------------ | ------------------------------- | ----------------------- |
+| `git-preamble`     | Ensure clean main + pull latest | Before ANY operation    |
+| `git-start-write`  | Preamble + create branch        | Before write operations |
+| `git-finish-write` | Commit + PR + return to main    | After write operations  |
 
 ### Read Operations (search, load, list)
 
 ```bash
-droid config codex | droid exec droid-codex git-preamble --config -
+droid config codex | droid exec codex git-preamble --config -
 # Then proceed with the read
 ```
 
@@ -60,12 +72,12 @@ droid config codex | droid exec droid-codex git-preamble --config -
 
 ```bash
 # 1. Start write (runs preamble + creates branch)
-droid config codex | droid exec droid-codex git-start-write --config - --branch codex/{action}-{name}
+droid config codex | droid exec codex git-start-write --config - --branch codex/{action}-{name}
 
 # 2. Make your changes (write files)
 
 # 3. Finish write (commit + PR + return to main)
-droid config codex | droid exec droid-codex git-finish-write --config - \
+droid config codex | droid exec codex git-finish-write --config - \
   --message "{commit message}" \
   --pr-title "{PR title}" \
   --pr-body "{PR description}"
@@ -76,11 +88,13 @@ The scripts return JSON with success/failure status. Check the result before pro
 ### Error Handling
 
 The scripts handle errors internally:
+
 - Silent recovery for transient issues
 - Clear error messages in JSON output
 - Automatic return to main even on partial failure
 
 If a script fails, check the JSON `error` field and report a user-friendly message:
+
 - "I hit a sync issue with the codex. Let me try again..."
 - Only escalate as last resort: "The codex repo needs manual attention."
 
@@ -134,44 +148,44 @@ fi
 
 **ALWAYS read `~/.droid/skills/codex/overrides.yaml` first.**
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `codex_repo` | `~/src/github.com/orderful-codex` | Path to local codex repo |
-| `freshness_days` | `30` | Days before staleness warning |
+| Setting          | Default                           | Description                   |
+| ---------------- | --------------------------------- | ----------------------------- |
+| `codex_repo`     | `~/src/github.com/orderful-codex` | Path to local codex repo      |
+| `freshness_days` | `30`                              | Days before staleness warning |
 
 ## Categories
 
 The codex has five categories:
 
-| Category | Path | Purpose |
-|----------|------|---------|
-| `projects` | `{codex_repo}/projects/` | Feature/project context (PRD, tech design, decisions) |
-| `domains` | `{codex_repo}/domains/` | Business domain knowledge - the "what" and "why" |
-| `proposals` | `{codex_repo}/proposals/` | Ideas and future direction - not yet committed |
-| `patterns` | `{codex_repo}/patterns/` | Cross-cutting technical patterns |
-| `topics` | `{codex_repo}/topics/` | Explored codebase areas with freshness tracking |
+| Category    | Path                      | Purpose                                               |
+| ----------- | ------------------------- | ----------------------------------------------------- |
+| `projects`  | `{codex_repo}/projects/`  | Feature/project context (PRD, tech design, decisions) |
+| `domains`   | `{codex_repo}/domains/`   | Business domain knowledge - the "what" and "why"      |
+| `proposals` | `{codex_repo}/proposals/` | Ideas and future direction - not yet committed        |
+| `patterns`  | `{codex_repo}/patterns/`  | Cross-cutting technical patterns                      |
+| `topics`    | `{codex_repo}/topics/`    | Explored codebase areas with freshness tracking       |
 
 ## Commands
 
-| Command | Action |
-|---------|--------|
-| `/codex` | Show categories overview |
-| `/codex projects` | List all projects |
-| `/codex domains` | List all domains |
-| `/codex proposals` | List all proposals |
-| `/codex patterns` | List all patterns |
-| `/codex topics` | List all topics |
-| `/codex {name}` | Load entry (searches all categories) |
-| `/codex search {query}` | Search across everything |
-| `/codex new {name}` | Scaffold new project (shorthand) |
-| `/codex new project {name}` | Scaffold new project from templates |
-| `/codex new domain {name}` | Scaffold new domain entry |
-| `/codex new proposal {name}` | Scaffold new proposal entry |
-| `/codex new pattern {name}` | Scaffold new pattern entry |
-| `/codex new topic {name}` | Scaffold new topic entry |
-| `/codex decision {text}` | Append to active project's DECISIONS.md |
-| `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent) |
-| `/codex artifact {file} {project}` | Add supporting artifact to project (uses agent) |
+| Command                                | Action                                          |
+| -------------------------------------- | ----------------------------------------------- |
+| `/codex`                               | Show categories overview                        |
+| `/codex projects`                      | List all projects                               |
+| `/codex domains`                       | List all domains                                |
+| `/codex proposals`                     | List all proposals                              |
+| `/codex patterns`                      | List all patterns                               |
+| `/codex topics`                        | List all topics                                 |
+| `/codex {name}`                        | Load entry (searches all categories)            |
+| `/codex search {query}`                | Search across everything                        |
+| `/codex new {name}`                    | Scaffold new project (shorthand)                |
+| `/codex new project {name}`            | Scaffold new project from templates             |
+| `/codex new domain {name}`             | Scaffold new domain entry                       |
+| `/codex new proposal {name}`           | Scaffold new proposal entry                     |
+| `/codex new pattern {name}`            | Scaffold new pattern entry                      |
+| `/codex new topic {name}`              | Scaffold new topic entry                        |
+| `/codex decision {text}`               | Append to active project's DECISIONS.md         |
+| `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent)       |
+| `/codex artifact {file} {project}`     | Add supporting artifact to project (uses agent) |
 
 ## Loading an Entry
 
@@ -181,7 +195,7 @@ The codex has five categories:
 
 1. **Run preamble first:**
    ```bash
-   droid config codex | droid exec droid-codex git-preamble --config -
+   droid config codex | droid exec codex git-preamble --config -
    ```
 2. **Read `{codex_repo}/index.yaml`** - this contains all entry names and aliases for fast lookup
 3. Match `{name}` against index keys and aliases (case-insensitive, partial match)
@@ -199,10 +213,11 @@ The codex has five categories:
 **Progressive disclosure:** CONTEXT.md is the first layer - a synthesised summary (~2KB) that handles most queries. Only load full PRD/TECH-DESIGN/DECISIONS files when deeper detail is explicitly needed. This avoids loading 30KB+ of docs for simple context questions.
 
 **If no CONTEXT.md exists for a project:**
-- Spawn background agent to synthesise (non-blocking)
-- Immediately ask user which file to load - don't make them wait
-- Background agent: reads PRD.md + TECH-DESIGN.md + DECISIONS.md, synthesises, creates PR
-- Notify user when complete: "CONTEXT.md ready - PR #{number}"
+
+- Synthesise one from PRD.md + TECH-DESIGN.md + DECISIONS.md
+- Create branch, commit CONTEXT.md, open PR
+- Output the new CONTEXT.md with "need more detail?" options
+- **OPTIONAL:** You may use a background agent (Task tool with `run_in_background: true`) to avoid blocking the user, but synchronous generation is fine too
 
 Full procedure: `references/loading.md`
 
@@ -225,6 +240,7 @@ codebase_paths:
 ```
 
 **Status values (unified across all categories):**
+
 - `draft` - Initial capture, not ready for consumption
 - `active` - Current, being used for implementation
 - `complete` - Project shipped, kept for reference
@@ -316,6 +332,7 @@ The main conversation handles: git branch, commit, PR creation, user interaction
 **Trigger:** `/codex artifact {file} {project}` or user wants to add supporting material to a project
 
 Artifacts are supplementary documents that support a project but aren't core document types (PRD, TECH-DESIGN, DECISIONS). Examples:
+
 - Customer interviews / transcripts
 - Research notes
 - Meeting summaries
@@ -409,6 +426,7 @@ The codex holds **shared** organizational knowledge. The `/project` skill holds
 ```
 
 When user runs `/project create --from codex:{name}`:
+
 1. Load the codex entry
 2. Extract key context for personal PROJECT.md
 3. Create project in user's projects_dir
@@ -418,6 +436,7 @@ When user runs `/project create --from codex:{name}`:
 **See "Git Hygiene (CRITICAL)" section above.** All codex changes go through PRs (main branch is protected).
 
 **Key points:**
+
 - Always run the preamble before any operation (ensures clean main + latest)
 - Write operations: branch → commit → PR → **return to main**
 - Safe changes (new files, decision appends) auto-merge via GitHub Action

package/{dist/tools/codex/skills/droid-codex → src/tools/codex/skills/codex}/references/loading.md

@@ -36,6 +36,7 @@ Detailed procedure for loading entries from the codex.
    - Multiple matches → show list with category, let user pick
 
 **Fallback:** If `index.yaml` doesn't exist, fall back to directory scanning:
+
 ```bash
 ls {codex_repo}/projects/ | grep -i {name}
 ls {codex_repo}/domains/ | grep -i {name}
@@ -59,11 +60,11 @@ projects/transaction-templates/
 
 CONTEXT.md is the **first layer** - a synthesised summary that's enough for most queries. Only load full documents when deeper detail is needed.
 
-| Layer | What | When to use |
-|-------|------|-------------|
-| 1 | CONTEXT.md (~2KB) | General questions, getting oriented, "what is this project?" |
-| 2 | Specific file | Deep dives - "show me the full technical architecture" |
-| 3 | All files | Comprehensive review, major updates, onboarding |
+| Layer | What              | When to use                                                  |
+| ----- | ----------------- | ------------------------------------------------------------ |
+| 1     | CONTEXT.md (~2KB) | General questions, getting oriented, "what is this project?" |
+| 2     | Specific file     | Deep dives - "show me the full technical architecture"       |
+| 3     | All files         | Comprehensive review, major updates, onboarding              |
 
 ### Procedure
 
@@ -71,6 +72,7 @@ CONTEXT.md is the **first layer** - a synthesised summary that's enough for most
 2. **Check for CONTEXT.md:**
 
    **If CONTEXT.md exists:**
+
    ```
    📂 Loading transaction-templates
 
@@ -85,6 +87,7 @@ CONTEXT.md is the **first layer** - a synthesised summary that's enough for most
    - TECH-DESIGN.md - Architecture and implementation
    - DECISIONS.md - Decision log
    ```
+
    Load CONTEXT.md automatically. Only load additional files if user asks.
 
    **If no CONTEXT.md:**
@@ -125,83 +128,116 @@ topics/organization-hierarchy.md
 
 ## Auto-Generating CONTEXT.md
 
-If loading a project and no CONTEXT.md exists, generate it **asynchronously** so the user isn't blocked.
+If loading a project and no CONTEXT.md exists, generate it immediately.
 
 **User sees:**
+
 ```
 📂 Loading transaction-templates
 
-No CONTEXT.md found - I'll generate one in the background.
-Meanwhile, which file do you want to load?
+No CONTEXT.md found - generating summary from available artifacts...
 
-Available files:
-- PRD.md - Full requirements and goals
-- TECH-DESIGN.md - Architecture and implementation
-- DECISIONS.md - Decision log
+Reading PRD.md...
+  → Extracting problem statement, goals, success metrics
+Reading TECH-DESIGN.md...
+  → Extracting architecture overview, key decisions
+Reading DECISIONS.md...
+  → Extracting decision log summary
+
+Synthesising unified context...
 ```
 
 **Procedure:**
 
+Generate CONTEXT.md either synchronously or asynchronously:
+
+### Option A: Synchronous (works everywhere)
+
+1. **Inform user:** "No CONTEXT.md found - generating summary from available artifacts"
+2. **Read all available files:** PRD.md, TECH-DESIGN.md, DECISIONS.md
+3. **Generate unified summary** (see template below)
+4. **Create PR** (see git workflow below)
+5. **Output the new CONTEXT.md** with "need more detail?" options
+
+### Option B: Asynchronous (Claude Code only, optional)
+
 1. **Spawn background agent** to synthesize CONTEXT.md (non-blocking):
    ```
-   Use Task tool with subagent_type: "general-purpose" and run_in_background: true
+   Use Task tool with subagent_type: "general" and run_in_background: true
    Prompt: "Generate CONTEXT.md for {project} from PRD.md, TECH-DESIGN.md, DECISIONS.md. Create branch, commit, open PR."
    ```
 2. **Immediately ask user** which file to load (don't wait for synthesis)
 3. **Load selected file** and continue working
 4. **When background agent completes**, inform user: "CONTEXT.md ready - PR #{number}"
 
-### Background Agent Task
+**Choose whichever approach works best.** Synchronous is simpler and works everywhere. Asynchronous avoids blocking but requires background agent support.
 
-The background agent should:
+### CONTEXT.md Template
 
-1. **Read all available files:** PRD.md, TECH-DESIGN.md, DECISIONS.md
-2. **Generate unified summary:**
-   ```markdown
-   ---
-   title: {Project Name}
-   type: context
-   created: {today}
-   updated: {today}
-   confidence: high
-   source: implementation
-   ---
+Generate a unified summary from the project files:
 
-   # {Project Name} - Context
+```markdown
+---
+title: { Project Name }
+type: context
+created: { today }
+updated: { today }
+confidence: high
+source: implementation
+---
 
-   ## Overview
-   {Synthesised from PRD problem statement + goals}
+# {Project Name} - Context
 
-   ## Technical Approach
-   {Synthesised from TECH-DESIGN architecture + key decisions}
+## Overview
 
-   ## Key Decisions
-   {Summarised from DECISIONS.md}
+{Synthesised from PRD problem statement + goals}
 
-   ## Current Status
-   {Inferred from most recent updates}
+## Technical Approach
 
-   ---
-   *Auto-generated from PRD.md, TECH-DESIGN.md, and DECISIONS.md*
-   ```
-4. **Create PR:**
-   ```bash
-   cd {codex_repo}
-   git checkout -b auto/context-{project-name}
-   # Write CONTEXT.md
-   git add projects/{project}/CONTEXT.md
-   git commit -F - <<EOF
-   feat: auto-generate CONTEXT.md for {project}
-   EOF
-   git push -u origin auto/context-{project-name}
-   gh pr create --title "Auto-generated CONTEXT.md for {project}" --body "Synthesised from PRD, TECH-DESIGN, and DECISIONS."
-   ```
-5. **Return result** (background agent outputs to task output file):
-   ```
-   ✅ CONTEXT.md synthesised and PR #{number} created for {project}
-   ```
+{Synthesised from TECH-DESIGN architecture + key decisions}
+
+## Key Decisions
+
+{Summarised from DECISIONS.md}
 
-   The main conversation will be notified when the background task completes.
+## Current Status
+
+{Inferred from most recent updates}
+
+---
+
+_Auto-generated from PRD.md, TECH-DESIGN.md, and DECISIONS.md_
+```
+
+### Git Workflow for CONTEXT.md
+
+After generating the CONTEXT.md content:
+
+```bash
+cd {codex_repo}
+git checkout -b auto/context-{project-name}
+# Write CONTEXT.md to projects/{project}/CONTEXT.md
+git add projects/{project}/CONTEXT.md
+git commit -F - <<EOF
+feat: auto-generate CONTEXT.md for {project}
+EOF
+git push -u origin auto/context-{project-name}
+gh pr create --title "Auto-generated CONTEXT.md for {project}" --body "Synthesised from PRD, TECH-DESIGN, and DECISIONS."
+```
+
+Then inform the user:
+
+```
+✅ CONTEXT.md created and PR #{number} opened
+
+[Show CONTEXT.md content]
+
+---
+Need more detail? Available files:
+- PRD.md - Full requirements and goals
+- TECH-DESIGN.md - Architecture and implementation
+- DECISIONS.md - Decision log
+```
 
 ## Freshness Checking
 
@@ -219,16 +255,19 @@ After loading any file:
      Want me to verify it's still accurate?
      ```
 4. **Check codebase changes** (if `codebase_paths` present):
+
    ```bash
    cd {workspace}
    git log --oneline --since="{updated}" -- {codebase_paths}
    ```
+
    - If commits found:
      ```
      ⚠️ Files in {paths} have changed since this doc was updated.
      Recent commits: {list}
      Want me to review for needed updates?
      ```
+
 5. **Note confidence** (if `confidence: low`):
    ```
    ℹ️ This was a quick exploration and may be incomplete.

package/src/tools/comments/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "droid-comments",
-  "version": "0.2.6",
+  "version": "0.3.0",
   "description": "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration.",
   "author": {
     "name": "Orderful",

package/src/tools/comments/TOOL.yaml

@@ -1,14 +1,15 @@
 name: comments
 description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
-version: 0.2.6
+version: 0.3.0
 status: beta
 
 includes:
   skills:
-    - name: droid-comments
+    - name: comments
       required: true
   commands:
-    - comments
+    - name: comments
+      is_alias: false
   agents: []
 
 dependencies: []

package/src/tools/comments/commands/comments.md

@@ -1,29 +1,27 @@
 ---
-description: Check and respond to inline @droid comments in code and docs
+name: comments
+description: "Check and respond to inline @droid comments in code and docs"
 argument-hint: "[check [{path}] | cleanup]"
-allowed-tools: [Read, Edit, Grep, Glob, Bash(git diff:*), Bash(git status:*)]
 ---
 
-# /comments - Check and respond to inline comments
+# /comments
 
-Entry point for inline comment workflows. See the **comments skill** for full behavior.
+**User invoked:** `/comments $ARGUMENTS`
 
-## Arguments
+**Your task:** Invoke the **comments skill** with these arguments.
 
-$ARGUMENTS
+## Examples
 
-## Usage
+- `/comments` → Check all files in current directory for @droid markers
+- `/comments check src/lib` → Check specific directory for @droid markers
+- `/comments cleanup` → Remove resolved comment threads
+
+## Quick Reference
 
 ```
 /comments              # Check all files in cwd
-/comments check        # Same as above
 /comments check {path} # Check specific file or directory
 /comments cleanup      # Remove resolved comment threads
 ```
 
-## Behavior
-
-Refer to the comments skill for:
-- **Check**: How to find markers, determine intent (action vs question), respond appropriately
-- **Cleanup**: How to identify resolved threads and summarize decisions
-- **Configuration**: `user_mention`, `ai_mentions`, `preserve_comments` settings
+See the **comments skill** for complete documentation and procedures.

package/{dist/tools/comments/skills/droid-comments → src/tools/comments/skills/comments}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: droid-comments
+name: comments
 description: "Inline conversations using @droid/@user markers in any file. Use when leaving async questions in code or having discussion that should stay near the code. User prompts like 'check for comments', 'address the @droid markers', 'clean up resolved comments'."
 globs:
   - "**/*"
@@ -83,6 +83,7 @@ When you find a `@droid` marker:
 **Use a two-pass approach for coherent responses:**
 
 #### Pass 1: Read & Analyse
+
 1. **Read config first:** Check `~/.droid/skills/comments/overrides.yaml` for `preserve_comments` setting (default: `true`)
 2. Search for ALL `> @droid` comments (and any configured `ai_mentions`) in the specified scope
 3. If there's a `git diff`, check those files first for relevant context
@@ -91,6 +92,7 @@ When you find a `@droid` marker:
 6. Note any contradictions or tensions to address
 
 #### Pass 2: Respond & Write
+
 1. For each comment, determine intent:
    - **Action request** ("do X", "add Y", "fix Z") → Execute the action
    - **Question** ("what do you think", "should we") → Respond with `> @{user_mention}`

package/src/tools/project/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "droid-project",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features.",
   "author": {
     "name": "Orderful",

package/src/tools/project/TOOL.yaml

@@ -1,14 +1,15 @@
 name: project
 description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
-version: 0.2.0
+version: 0.3.0
 status: beta
 
 includes:
   skills:
-    - name: droid-project
+    - name: project
       required: true
   commands:
-    - project
+    - name: project
+      is_alias: false
   agents: []
 
 dependencies: []

package/src/tools/project/commands/project.md

@@ -1,45 +1,30 @@
 ---
-description: Manage project context files for persistent AI memory across sessions
+name: project
+description: "Manage project context files for persistent AI memory across sessions"
 argument-hint: "[{keywords} | update | create {name}]"
-allowed-tools: [Read, Write, Edit, Glob, Bash(mkdir:*), Bash(ls:*)]
 ---
 
 # /project
 
-Entry point for project context management. See the **project skill** for full behavior.
+**User invoked:** `/project $ARGUMENTS`
 
-## Arguments
+**Your task:** Invoke the **project skill** with these arguments.
 
-$ARGUMENTS
+## Example
 
-## Default Behavior
+If user typed `/project droid`, you should interpret this as: "Search for and load a project matching 'droid'"
 
-**IMPORTANT:** When given keywords (e.g., `/project audit-log`), the default action is to **SEARCH** for existing projects, NOT create. Only create a project when the `create` keyword is explicitly used.
+If user typed `/project create new-feature`, interpret as: "Create a new project named 'new-feature'"
 
-## Usage
+## Quick Reference
 
 ```
 /project                    # List and select a project
-/project {keywords}         # SEARCH: Fuzzy-match and load existing project
+/project {keywords}         # SEARCH for existing project (default action)
 /project update             # Update from conversation context
-/project update {name}      # Update specific project
-/project create             # Create new project interactively
-/project create {name}      # Create with name (requires "create" keyword)
+/project create {name}      # CREATE new project
 ```
 
-## Configuration
+**Default behavior:** When given keywords, SEARCH first (don't create unless "create" keyword is present).
 
-**ALWAYS read `~/.droid/skills/project/overrides.yaml` first.**
-
-- If `projects_dir` is set → use **ONLY** that path (do NOT also search defaults)
-- If not configured → use the default for current AI tool
-- `preset` - Template format: `markdown` or `obsidian`
-
-## Behavior
-
-Refer to the project skill for:
-- **Loading**: How to fuzzy-match, handle multiple matches, summarize after load
-- **Updating**: What to extract from conversation, versioning rules, changelog format
-- **Creating**: Template structure by preset, required files
-
-The skill's `references/` folder contains detailed specs for versioning, changelog formatting, and templates.
+See the **project skill** for complete documentation and procedures.