@ncoderz/awa 1.7.1 → 1.8.0

package/dist/renumber-ZCI2H5HZ.js

@@ -0,0 +1,9 @@
+#!/usr/bin/env node
+import {
+  renumberCommand
+} from "./chunk-WGGMDWBE.js";
+import "./chunk-LRQWZCYL.js";
+export {
+  renumberCommand
+};
+//# sourceMappingURL=renumber-ZCI2H5HZ.js.map

package/dist/renumber-ZCI2H5HZ.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@ncoderz/awa",
-  "version": "1.7.1",
+  "version": "1.8.0",
   "description": "awa is an Agent Workflow for AIs. It is also a CLI tool to powerfully manage agent workflow files using templates.",
-  "license": "MIT",
+  "license": "BSD-3-Clause",
   "repository": {
     "type": "git",
     "url": "https://github.com/ncoderz/awa"
@@ -25,9 +25,9 @@
     "test:watch": "vitest",
     "test:coverage": "vitest run --coverage",
     "check": "npm run dev -- check",
-    "lint": "biome check --error-on-warnings .",
-    "lint:fix": "biome check --error-on-warnings --fix .",
-    "format": "biome format --write .",
+    "lint": "eslint --max-warnings 0 .",
+    "lint:fix": "eslint --max-warnings 0 --fix .",
+    "format": "prettier --write .",
     "typecheck": "tsc --noEmit",
     "typecheck:tests": "tsc --noEmit -p tsconfig.test.json",
     "typecheck:all": "npm run typecheck && npm run typecheck:tests",
@@ -71,15 +71,22 @@
     "yaml": "^2.8.2"
   },
   "devDependencies": {
-    "@biomejs/biome": "^2",
+    "@eslint/js": "^10.0.1",
+    "@eslint/json": "^1.0.1",
     "@types/degit": "^2.8.6",
     "@types/mdast": "^4.0.4",
     "@types/node": "^25.3.0",
     "@vitest/coverage-v8": "^4.0.18",
+    "eslint": "^10.0.2",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-prettier": "^5.5.5",
+    "eslint-plugin-simple-import-sort": "^12.1.1",
     "fast-check": "^4.5.3",
+    "prettier": "^3.8.1",
     "tsup": "^8.5.1",
     "tsx": "^4.21.0",
     "typescript": "^5.9.3",
+    "typescript-eslint": "^8.56.1",
     "vitest": "^4.0.18"
   }
 }

package/templates/awa/.agent/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('agy')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.agent/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('agy')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.agent/workflows/spec-merge.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('agy')) { %>
+<%~ include('_partials/_cmd.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.agent/workflows/spec-tidy.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('agy')) { %>
+<%~ include('_partials/_cmd.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.agents/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('codex')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.agents/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('codex')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.awa/.agent/schemas/ALIGN_REPORT.schema.yaml

@@ -6,7 +6,7 @@ description: >
   (CERTAIN/LIKELY/UNCERTAIN), and type (MISSING/DIFFERENCE/CONFLICT/INCOMPLETE/
   UNTESTED/ORPHAN/SUPERSET). Findings are checkbox items with SOURCE, TARGET,
   ISSUE, and RESOLUTION fields. Summary section has severity counts and STATUS.
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading

package/templates/awa/.awa/.agent/schemas/API.schema.yaml

@@ -4,4 +4,4 @@ description: >
   TypeSpec API specification. Defines major APIs using TypeSpec format
   conventions. Write in TypeSpec unless explicitly requested otherwise.
   One file per API surface area, named with the feature CODE prefix.
-line-limit: 500
+line-limit: 800

package/templates/awa/.awa/.agent/schemas/ARCHITECTURE.schema.yaml

@@ -32,6 +32,13 @@ sections:
       Bullet list of software layers or subsystems (e.g., CLI Layer,
       Core Engine, Template System, I/O Layer).
 
+  # Feature Codes section (auto-generated by awa check)
+  - heading: "Feature Codes"
+    level: 2
+    description: >
+      Auto-generated table of feature codes, feature names, and scope boundaries.
+      Managed by `awa check` — do not edit manually.
+
   # Technology Stack section
   - heading: "Technology Stack"
     level: 2

package/templates/awa/.awa/.agent/schemas/DESIGN.schema.yaml

@@ -6,7 +6,7 @@ description: >
   Each component has a name ({CODE}-{ComponentName}), description, IMPLEMENTS
   trace, and interface code block. Correctness properties use {CODE}_P-{n} IDs
   and link back to requirements via VALIDATES.
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading: "Design Specification"

package/templates/awa/.awa/.agent/schemas/{EXAMPLES.schema.yaml → EXAMPLE.schema.yaml}

@@ -1,13 +1,13 @@
-# Structural rules for EXAMPLES-{CODE}-{feature-name}-{nnn}.md files
-target-files: ".awa/specs/EXAMPLES-*.md"
+# Structural rules for EXAMPLE-{CODE}-{feature-name}-{nnn}.md files
+target-files: ".awa/specs/EXAMPLE-*.md"
 description: >
   Concrete usage examples for a feature. Detailed, hands-on, reproducible.
   Use the same {CODE} as the corresponding FEAT/REQ for the feature.
-  Number files sequentially (-001, -002, ...) when splitting at the 500-line limit.
+  Number files sequentially (-001, -002, ...) when splitting at the line-limit.
   Each example must have a title, context, and code/demonstration block.
   Marked [INFORMATIVE]. Prohibited: normative language (SHALL/SHOULD/MAY),
   acceptance criteria, traceability IDs, design decisions.
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading with INFORMATIVE marker

package/templates/awa/.awa/.agent/schemas/FEAT.schema.yaml

@@ -6,7 +6,7 @@ description: >
   to distinguish from normative REQ/DESIGN documents.
   Prohibited: normative language (SHALL/SHOULD/MAY), acceptance criteria,
   traceability IDs, design decisions, bold formatting.
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading with INFORMATIVE marker
@@ -33,6 +33,13 @@ sections:
       How users should think about this feature. Mental model, key abstractions,
       and relationships between concepts. May include diagrams.
 
+  # Scope Boundary section (optional, after Conceptual Model)
+  - heading: "Scope Boundary"
+    level: 2
+    description: >
+      Single sentence defining the feature's scope boundary — what this feature
+      owns and where it ends.
+
   # Scenarios section with repeatable scenario headings
   - heading: "Scenarios"
     level: 2

package/templates/awa/.awa/.agent/schemas/PLAN.schema.yaml

@@ -7,7 +7,7 @@ description: >
   organize sections as the plan demands. Plans should not contain significant
   code (short snippets for explanation are fine).
   Traceability links to REQ/DESIGN/code/tests are optional but encouraged.
-line-limit: 500
+line-limit: 800
 
 sections:
   # H1 title with status/direction metadata

package/templates/awa/.awa/.agent/schemas/README.schema.yaml

@@ -5,7 +5,7 @@ description: >
   /docs folder rather than including lengthy content inline. Required sections:
   title, description, installation, and usage. Keep it concise — the README
   is the front door, not the whole house.
-line-limit: 500
+line-limit: 800
 
 sections:
   # Project title (H1)

package/templates/awa/.awa/.agent/schemas/REQ.schema.yaml

@@ -6,7 +6,7 @@ description: >
   Each requirement has an ID ({CODE}-{n}), a user story (AS A/I WANT/SO THAT),
   and acceptance criteria with INCOSE-compliant types.
   Subrequirements use dotted IDs ({CODE}-{n}.{p}).
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading: "Requirements Specification"

package/templates/awa/.awa/.agent/schemas/TASK.schema.yaml

@@ -9,7 +9,7 @@ description: >
   A Documentation phase is required after Polish. It lists doc files to update
   (README.md, docs/) for user-facing changes. If no doc updates are needed,
   include a single task stating so (e.g., "No doc changes — internal only").
-line-limit: 500
+line-limit: 800
 
 sections:
   # Top-level heading: "Implementation Tasks"

package/templates/awa/.claude/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('claude')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.claude/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('claude')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.gemini/commands/spec-merge.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('gemini')) { %>
+<%~ include('_partials/_cmd.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.gemini/commands/spec-tidy.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('gemini')) { %>
+<%~ include('_partials/_cmd.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.gemini/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('gemini')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.gemini/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('gemini')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.github/prompts/awa.spec-merge.prompt.md

@@ -0,0 +1,8 @@
+<% if (it.features.includes('copilot')) { %>
+---
+description: Merge two feature codes into one using awa spec merge
+argument-hint: "<source-code> <target-code>"
+---
+
+<%~ include('_partials/awa.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.github/prompts/awa.spec-tidy.prompt.md

@@ -0,0 +1,7 @@
+<% if (it.features.includes('copilot')) { %>
+---
+description: Tidy and reorganise the specifications logically
+---
+
+<%~ include('_partials/awa.spec.tidy.md', it) %>
+<% } %>

package/templates/awa/.github/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('copilot')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.github/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('copilot')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.kilocode/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('kilocode')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.kilocode/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('kilocode')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.kilocode/workflows/spec-merge.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('kilocode')) { %>
+<%~ include('_partials/_cmd.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.kilocode/workflows/spec-tidy.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('kilocode')) { %>
+<%~ include('_partials/_cmd.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.opencode/commands/spec-merge.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('opencode')) { %>
+<%~ include('_partials/_cmd.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.opencode/commands/spec-tidy.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('opencode')) { %>
+<%~ include('_partials/_cmd.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.opencode/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('opencode')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.opencode/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('opencode')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.qwen/commands/spec-merge.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('qwen')) { %>
+<%~ include('_partials/_cmd.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.qwen/commands/spec-tidy.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('qwen')) { %>
+<%~ include('_partials/_cmd.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.qwen/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('qwen')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.qwen/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('qwen')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.roo/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('roo')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.roo/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('roo')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/.windsurf/skills/spec-merge/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('windsurf')) { %>
+<%~ include('_partials/_skill.spec-merge.md', it) %>
+<% } %>

package/templates/awa/.windsurf/skills/spec-tidy/SKILL.md

@@ -0,0 +1,3 @@
+<% if (it.features.includes('windsurf')) { %>
+<%~ include('_partials/_skill.spec-tidy.md', it) %>
+<% } %>

package/templates/awa/_delete.txt

@@ -24,6 +24,10 @@
 .awa/.agent/schemas/REQ.schema.md
 .awa/.agent/schemas/TASK.schema.md
 
+# Old yaml schemas
+.awa/.agent/schemas/EXAMPLES.schema.yaml
+
+
 # @feature copilot
 .github/agents/awa.agent.md
 .github/prompts/awa.architecture.prompt.md

package/templates/awa/_partials/_cmd.spec-merge.md

@@ -0,0 +1,6 @@
+---
+description: Merge two feature codes into one using awa spec merge
+argument-hint: "<source-code> <target-code>"
+---
+
+<%~ include('awa.spec-merge.md', it) %>

package/templates/awa/_partials/_cmd.spec-tidy.md

@@ -0,0 +1,5 @@
+---
+description: Tidy and reorganise the specifications logically
+---
+
+<%~ include('awa.spec.tidy.md', it) %>

package/templates/awa/_partials/_skill.spec-merge.md

@@ -0,0 +1,6 @@
+---
+name: spec-merge
+description: Merge two feature codes into one. Use this when asked to combine, merge, or consolidate feature codes.
+---
+
+<%~ include('awa.spec-merge.md', it) %>

package/templates/awa/_partials/_skill.spec-tidy.md

@@ -0,0 +1,6 @@
+---
+name: spec-tidy
+description: Tidy and reorganise the specifications logically. Use this when asked to tidy or reorganise the specifications.
+---
+
+<%~ include('awa.spec.tidy.md', it) %>

package/templates/awa/_partials/awa.align.md

@@ -34,7 +34,7 @@ y = target artifact (what x is validated against) = requirement(s).
 
 <file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="api" path=".awa/specs/API-{CODE}-{feature-name}.md" required="if relevant" />

package/templates/awa/_partials/awa.brainstorm.md

@@ -20,7 +20,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 <file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="api" path=".awa/specs/API-{CODE}-{feature-name}.md" required="if relevant" />

package/templates/awa/_partials/awa.code.md

@@ -20,7 +20,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 <file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="api" path=".awa/specs/API-{CODE}-{feature-name}.md" required="if relevant" />

package/templates/awa/_partials/awa.core.md

@@ -9,12 +9,13 @@ YOU follow the set of rules defined below, reminding yourself of the rules perio
 </workflow>
 
 <file_structure>
+```
   .awa/
   ├── .agent/
   │   └── schemas/
   │       ├── ARCHITECTURE.schema.yaml
   │       ├── FEAT.schema.yaml
-  │       ├── EXAMPLES.schema.yaml
+  │       ├── EXAMPLE.schema.yaml
   │       ├── REQ.schema.yaml
   │       ├── DESIGN.schema.yaml
   │       ├── API.schema.yaml
@@ -25,7 +26,7 @@ YOU follow the set of rules defined below, reminding yourself of the rules perio
   ├── specs/
   │   ├── ARCHITECTURE.md
   │   ├── FEAT-{CODE}-{feature-name}.md
-  │   ├── EXAMPLES-{CODE}-{feature-name}-{nnn}.md
+  │   ├── EXAMPLE-{CODE}-{feature-name}-{nnn}.md
   │   ├── REQ-{CODE}-{feature-name}.md
   │   ├── DESIGN-{CODE}-{feature-name}.md
   │   └── API-{CODE}-{api-name}.tsp
@@ -37,12 +38,13 @@ YOU follow the set of rules defined below, reminding yourself of the rules perio
   │   └── ALIGN-{x}-WITH-{y}-{nnn}.md
   └── rules/
       └── *.md
+```
 </file_structure>
 
 <file_descriptions>
 - ARCHITECTURE.md: High-level architecture overview of the project.
 - FEAT-{CODE}-{feature-name}.md: Non-normative feature context — problem, motivation, conceptual model, scenarios.
-- EXAMPLES-{CODE}-{feature-name}-{nnn}.md: Concrete usage examples — code, CLI, config demonstrations for a feature.
+- EXAMPLE-{CODE}-{feature-name}-{nnn}.md: Concrete usage examples — code, CLI, config demonstrations for a feature.
 - REQ-{CODE}-{feature-name}.md: Requirements in EARS format (INCOSE-compliant).
 - DESIGN-{CODE}-{feature-name}.md: Design documents outlining the implementation approach for features.
 - API-{CODE}-{api-name}.tsp: TypeSpec files defining major APIs.
@@ -53,6 +55,7 @@ YOU follow the set of rules defined below, reminding yourself of the rules perio
 </file_descriptions>
 
 <traceability_chain>
+```
 {CODE}-{n} = requirement id, e.g. DIFF-1; subrequirement id = {CODE}-{n}.{p}, e.g. DIFF-1.1
 {CODE}-{n}[.{p}]_AC-{m} = acceptance criterion id, e.g. DIFF-1_AC-1 or DIFF-1.1_AC-2
 {CODE}_P-{n} = correctness property id, e.g. DIFF_P-2
@@ -84,10 +87,11 @@ DESIGN-{CODE}-{feature}.md
   └── @awa-test: {CODE}-{n}[.{p}]_AC-{m}    // verifies AC directly
 
 Markers create the trace, not file paths.
+```
 </traceability_chain>
 
 <file_size_limits>
-Any file exceeding schema defined line-limit, or otherwise 500 lines, MUST be split logically into multiple files unless impossible. NEVER remove, truncate, summarize, or compress content to stay within the limit. Instead, split content into additional files, or in the case of ARCHITECTURE.md, push details to other spec files.
+Any file exceeding schema defined line-limit, or otherwise 800 lines, MUST be split logically into multiple files unless impossible. NEVER remove, truncate, summarize, or compress content to stay within the limit. Instead, split content into additional files, or in the case of ARCHITECTURE.md, push details to other spec files.
 </file_size_limits>
 
 <core_principles>

package/templates/awa/_partials/awa.design.md

@@ -22,7 +22,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 <file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="api" path=".awa/specs/API-{CODE}-{feature-name}.md" required="if relevant" />
@@ -41,6 +41,8 @@ If deriving from existing code (reverse workflow), analyze the codebase to extra
 
 ## Rules
 
+You SHALL ensure the {CODE} matches the corresponding REQ {CODE} for the same feature if one exists.
+You SHALL run `awa spec codes` to help choose the {CODE} extending existing one if logical.
 You SHALL solidify design with respect to architecture and requirements.
 You SHALL create and maintain design specifications for features.
 You SHALL create and maintain API specifications in TypeSpec format.
@@ -49,7 +51,6 @@ You SHALL identify existing requirements to update, or new requirements to creat
 You SHALL consider edge cases, UX, technical constraints, success criteria.
 You MUST identify areas where research is needed based on the feature requirements.
 You MUST conduct research and build up context in the conversation thread.
-You SHALL ensure the 3-letter {CODE} used in the filename is unique within the project.
 You SHALL ensure IMPLEMENTS and VALIDATES cross-references in design components resolve to real requirement IDs and AC IDs.
 You SHALL support reverse workflow: deriving design from existing code when requested.
 You SHALL clarify open points with user.

package/templates/awa/_partials/awa.documentation.md

@@ -56,7 +56,7 @@ docs/
    - Each file covers one topic
    - Reference style for commands/APIs
    - Tutorial style for guides
-   - Keep files under 500 lines; split if larger
+   - Keep files under the specified line-limit; split if larger
 
 3. Derive from specifications
    - Do not duplicate; summarize and link

package/templates/awa/_partials/awa.examples.md

@@ -6,7 +6,7 @@
  <read path=".awa/.agent/awa.core.md" required="true" error="on not found" />
  <read path=".awa/rules/*.md" required="true" />
  <read path=".awa/specs/ARCHITECTURE.md" required="if exists" />
- <read path=".awa/.agent/schemas/EXAMPLES.schema.yaml" required="true" error="on not found" />
+ <read path=".awa/.agent/schemas/EXAMPLE.schema.yaml" required="true" error="on not found" />
 </tool>
 
 ## User Input
@@ -23,7 +23,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if updating" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if updating" />
 <file type="code" required="if relevant" />
 
 ## Action
@@ -34,7 +34,7 @@ If deriving from existing code (reverse workflow), extract representative usage
 
 ## Outputs
 
-<file path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" />
+<file path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" />
 
 ## Rules
 
@@ -42,7 +42,7 @@ You SHALL provide concrete, detailed, reproducible examples (code, CLI, config).
 You SHALL include context for each example explaining when to use it and what it demonstrates.
 You SHALL use the same {CODE} as the corresponding FEAT/REQ for the feature.
 You SHALL mark the document as INFORMATIVE (not normative).
-You SHALL split into multiple files (-001, -002, ...) if a single file would exceed 500 lines.
+You SHALL split into multiple files (-001, -002, ...) if a single file would exceed the line-limit.
 You SHALL NOT use normative language (SHALL/SHOULD/MAY) — that belongs in REQ documents.
 You SHALL NOT define acceptance criteria or traceability IDs — that belongs in REQ documents.
 You SHALL NOT describe design decisions or implementation details — that belongs in DESIGN documents.

package/templates/awa/_partials/awa.feature.md

@@ -27,6 +27,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 ## Action
 
 Create or update a non-normative feature context document as specified in the instruction above, following awa conventions.
+Consider existing specifications before making changes.
 
 If deriving from existing code or requirements (reverse workflow), analyze the codebase and specs to extract the problem statement, conceptual model, and usage scenarios.
 
@@ -36,13 +37,13 @@ If deriving from existing code or requirements (reverse workflow), analyze the c
 
 ## Rules
 
+You SHALL run `awa spec codes` to help choose the {CODE} extending existing one if logical.
 You SHALL describe the problem, motivation, and conceptual model for the feature.
 You SHALL provide concrete usage scenarios that illustrate the feature in action.
 You SHALL mark the document as INFORMATIVE (not normative).
 You SHALL NOT use normative language (SHALL/SHOULD/MAY) — that belongs in REQ documents.
 You SHALL NOT define acceptance criteria or traceability IDs — that belongs in REQ documents.
 You SHALL NOT describe design decisions or implementation details — that belongs in DESIGN documents.
-You SHALL ensure the {CODE} matches the corresponding REQ {CODE} for the same feature.
 You SHALL use clear, accessible language; define jargon in a glossary if needed.
 You SHALL support reverse workflow: deriving feature context from existing code or requirements when requested.
 You SHALL clarify open points with user.

package/templates/awa/_partials/awa.plan.md

@@ -21,7 +21,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 <file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
 <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if relevant" />
-<file type="examples" path=".awa/specs/EXAMPLES-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
 <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="design" path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" required="if relevant" />
 <file type="api" path=".awa/specs/API-{CODE}-{feature-name}.md" required="if relevant" />
@@ -40,7 +40,7 @@ Update or create the ad-hoc plan document(s) as specified in the instruction abo
 You SHALL create and maintain ad-hoc plans for features, improvements, refactors, or other user requests.
 You SHALL break down work into detailed, actionable steps
 You SHALL identify risks, dependencies, and completion criteria
-You SHALL ensure the 3-letter {nnn} used in the filename follows the previous plans within the project.
+You SHALL ensure the 3-number {nnn} used in the filename follows the previous plans within the project.
 You SHOULD NOT write significant code in the plan documents. Code can be used to define data structures and for explanation.
 You SHOULD consider edge cases, user experience, technical constraints, and success criteria.
 You SHOULD suggest specific areas where the plan might need clarification or expansion.