@ncoderz/awa 1.0.0 → 1.2.0

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

@@ -1,61 +0,0 @@
-<schema target-files=".awa/specs/FEAT-{CODE}-{feature-name}.md">
-
-- Non-normative feature context. Explain what and why, not how.
-- Use clear, accessible language. Avoid jargon unless defined in glossary.
-- Required sections: problem, conceptual model, scenarios.
-- Optional sections: background, glossary, stakeholders, diagrams, non-normative notes.
-- Prohibited: normative language (SHALL/SHOULD/MAY), acceptance criteria, traceability IDs, design decisions.
-- Mark the document as INFORMATIVE (not normative).
-- Add metadata with change log.
-
-Example structure:
-
-```
-# Feature Context [INFORMATIVE]
-
-## Problem
-
-Why this feature exists. What pain point or gap it addresses.
-
-## Conceptual Model
-
-How users should think about this feature. Mental model, key abstractions.
-
-## Scenarios
-
-Concrete usage examples illustrating the feature in action.
-
-### Scenario 1: {title}
-{narrative}
-
-### Scenario 2: {title}
-{narrative}
-
-## Background
-
-Additional context: history, prior art, references.
-
-## Glossary
-
-- TERM: Definition
-
-## Stakeholders
-
-- ROLE: How they relate to this feature
-
-## Diagrams
-
-```mermaid
-{diagram}
-```
-
-## Non-Normative Notes
-
-Recommendations, best practices, or explanatory content that is not testable.
-
-## Change Log
-
-- {version} ({date}): {changes}
-```
-
-</schema>

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

@@ -1,8 +0,0 @@
-<schema target-files=".awa/plans/PLAN-{nnn}-{plan-name}.md">
-- Plan as already instructed, and:
-- Use as succinct language as possible
-- Add metadata:
-  - Status: "in-progress", "completed", "blocked"
-  - Workflow direction: "top-down", "bottom-up", "lateral"
-  - Traceability links to requirements/design/code/tests
-</schema>

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

@@ -1,133 +0,0 @@
-<schema target-file="README.md">
-
-```json
-{
-  "description": "Project README. Succinct language. User-facing. Link to detailed docs in /docs folder.",
-  "required": ["title", "description", "installation", "usage"],
-  "properties": {
-    "title": { "type": "project name" },
-    "badges": { "type": "array of badge markdown" },
-    "description": { "type": "one paragraph: what the project does and why" },
-    "features": { "type": "array of key features" },
-    "installation": {
-      "required": ["steps"],
-      "properties": {
-        "prerequisites": { "type": "array of requirements" },
-        "steps": { "type": "array of commands or instructions" }
-      }
-    },
-    "usage": {
-      "required": ["quickStart"],
-      "properties": {
-        "quickStart": { "type": "minimal example to get started" },
-        "examples": { "type": "array", "items": { "$ref": "#/$defs/example" } }
-      }
-    },
-    "documentation": { "type": "array of links to /docs files", "items": { "$ref": "#/$defs/docLink" } },
-    "contributing": { "type": "brief instructions or link to CONTRIBUTING.md" },
-    "license": { "type": "license name and link" },
-    "acknowledgments": { "type": "array of credits" }
-  },
-  "$defs": {
-    "example": {
-      "properties": {
-        "title": {},
-        "description": {},
-        "code": { "type": "code block" }
-      }
-    },
-    "docLink": {
-      "required": ["title", "path"],
-      "properties": {
-        "title": {},
-        "path": { "type": "relative path to /docs file" },
-        "description": {}
-      }
-    }
-  },
-  "$render": {
-    "template": "# {title}\\n\\n{badges?}\\n\\n{description}\\n\\n## Features\\n{features→'- {}'}\\n\\n## Installation\\n\\n### Prerequisites\\n{installation.prerequisites→'- {}'}\\n\\n### Install\\n{installation.steps→'```bash\\n{}\\n```'}\\n\\n## Usage\\n\\n{usage.quickStart}\\n\\n### Examples\\n{usage.examples→'#### {title}\\n{description?}\\n```\\n{CODE}\\n```'}\\n\\n## Documentation\\n{documentation→'- [{title}]({path}) — {description?}'}\\n\\n## Contributing\\n{contributing}\\n\\n## License\\n{license}\\n\\n## Acknowledgments\\n{acknowledgments→'- {}'}",
-    "omit": ["section if empty", "badges if absent", "Prerequisites if empty", "description in examples if absent", "Acknowledgments if empty"],
-    "prohibited": ["**bold** in section headers", "implementation details", "internal architecture", "excessive length — link to /docs instead"]
-  }
-}
-```
-
-<example>
-# awa CLI
-
-[![npm version](https://img.shields.io/npm/v/awa-cli.svg)](https://www.npmjs.com/package/awa-cli)
-[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
-
-awa CLI generates AI coding agent configuration files from templates, enabling developers to quickly scaffold consistent agent setups across projects.
-
-## Features
-
-- Template-based configuration generation
-- Feature flag support for conditional content
-- Multiple output formats (Markdown, YAML, JSON)
-- Diff mode to preview changes before applying
-- Local and remote template sources
-
-## Installation
-
-### Prerequisites
-
-- Node.js 20 or higher
-- npm or pnpm
-
-### Install
-
-```bash
-npm install -g awa-cli
-```
-
-## Usage
-
-```bash
-# Generate configuration from default template
-awa generate
-
-# Generate with specific features enabled
-awa generate --features typescript,testing
-
-# Preview changes without writing files
-awa diff
-```
-
-### Examples
-
-#### Custom Template
-
-```bash
-awa generate --template ./my-templates --output ./.ai
-```
-
-#### Feature Flags
-
-```bash
-awa generate --features strict,verbose --remove-features legacy
-```
-
-## Documentation
-
-- [Configuration Guide](docs/configuration.md) — Configure templates and options
-- [Template Authoring](docs/templates.md) — Create custom templates
-- [CLI Reference](docs/cli-reference.md) — Complete command documentation
-- [API Reference](docs/api.md) — Programmatic usage
-
-## Contributing
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
-
-## License
-
-[MIT](LICENSE)
-
-## Acknowledgments
-
-- Eta templating engine
-- Citty CLI framework
-</example>
-
-</schema>

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

@@ -1,125 +0,0 @@
-<schema target-files=".awa/specs/REQ-{CODE}-{feature-name}.md">
-
-```json
-{
-  "description": "Requirements only. Succinct language. Do not overspecify. Omit irrelevant information.",
-  "required": ["introduction", "requirements"],
-  "properties": {
-    "metadata": { "properties": { "changeLog": { "type": "array", "items": { "properties": { "version": {}, "date": {}, "changes": {} } } } } },
-    "introduction": { "type": "brief context for the requirements" },
-    "stakeholders": { "type": "array", "items": { "properties": { "role": {}, "description": {} } } },
-    "glossary": { "type": "object of term→definition" },
-    "requirements": { "type": "array", "items": { "$ref": "#/$defs/requirement" } },
-    "assumptions": { "type": "array of strings" },
-    "constraints": { "type": "array of strings" },
-    "outOfScope": { "type": "array of strings" }
-  },
-  "$defs": {
-    "requirement": {
-      "required": ["id", "title", "story", "criteria"],
-      "properties": {
-        "id": { "type": "pattern: {CODE}-{n} or {CODE}-{n}.{p} for subrequirements (e.g., CLI-3, ENG-1.1)" },
-        "title": { "type": "short title" },
-        "story": { "required": ["role", "want", "benefit"], "properties": { "role": {}, "want": {}, "benefit": {} } },
-        "criteria": { "type": "array", "items": { "$ref": "#/$defs/criterion" } },
-        "priority": { "enum": ["must", "should", "could", "wont"] },
-        "rationale": { "type": "why this requirement exists" },
-        "dependencies": { "type": "array of requirement IDs" },
-        "subrequirements": { "type": "array", "items": { "$ref": "#/$defs/requirement" } }
-      }
-    },
-    "criterion": {
-      "required": ["id", "type", "statement"],
-      "properties": {
-        "id": { "type": "pattern: {CODE}-{n}[.{p}]_AC-{m} for subrequirements (e.g., CLI-3_AC-1, ENG-1.1_AC-2)" },
-        "type": { "enum": ["ubiquitous", "event", "state", "conditional", "optional", "complex"] },
-        "statement": { "type": "testable statement using SHALL/SHOULD/MAY" },
-        "notes": { "type": "additional context" },
-        "testable": { "type": "boolean, default true" },
-        "verified": { "type": "boolean; true when validated as implemented and tested" }
-      }
-    }
-  },
-  "$render": {
-    "template": "# Requirements Specification\n\n## Introduction\n{introduction}\n\n## Glossary\n{glossary→'- {TERM}: {definition}'}\n\n## Stakeholders\n{stakeholders→'- {ROLE}: {description}'}\n\n## Requirements\n{requirements→'### {id}: {title} [{PRIORITY?}]\n\nAS A {story.role}, I WANT {story.want}, SO THAT {story.benefit}.\n\n> {rationale?}\n\nACCEPTANCE CRITERIA\n\n{criteria→\"- [{verified?x: }] {id} [{type}]: {statement} — {notes?} [untestable?]\"}\n\nDEPENDS ON: {dependencies?}'}\n\n## Assumptions\n{assumptions→'- {}'}\n\n## Constraints\n{constraints→'- {}'}\n\n## Out of Scope\n{outOfScope→'- {}'}\n\n## Change Log\n{metadata.changeLog→'- {version} ({date}): {changes}'}",
-    "omit": ["section if empty", "[PRIORITY] if absent", "rationale blockquote if absent", "— {notes} if absent", "[untestable] if testable true/absent", "DEPENDS ON if empty"],
-    "checkbox": "[x] if verified true, [ ] otherwise",
-    "prohibited": ["**bold** — use CAPITALS", "FieldName: value patterns", "nested bullets for story/criterion", "showing 'testable: true'", "headers for individual criteria"]
-  }
-}
-```
-
-<example>
-# Requirements Specification
-
-## Introduction
-
-Core engine requirements for game framework.
-
-## Glossary
-
-- GAME LOOP: Core cycle of update-render that drives the engine
-- CONTEXT: Runtime state container for engine subsystems
-
-## Stakeholders
-
-- GAME DEVELOPER: Builds games using the engine API
-- ENGINE MAINTAINER: Maintains and extends engine internals
-
-## Requirements
-
-### ENG-1: Core Engine Framework [MUST]
-
-AS A game developer, I WANT a game loop, SO THAT predictable execution.
-
-> Foundation for all games.
-
-ACCEPTANCE CRITERIA
-
-- [x] ENG-1_AC-1 [event]: WHEN engine initializes THEN system SHALL create context
-- [ ] ENG-1_AC-2 [event]: WHEN `--verbose` flag is provided THEN system SHALL enable debug logging — CLI flag
-- [ ] ENG-1_AC-3 [ubiquitous]: The system SHALL maintain 60fps minimum frame rate
-- [ ] ENG-1_AC-4 [event]: WHEN multiple `--preset` options are provided THEN system SHALL collect all values
-- [ ] ENG-1_AC-5 [conditional]: IF config contains a `[presets]` table THEN system SHALL parse it as a dictionary
-
-### ENG-1.1: Subsystem Registration [SHOULD]
-
-AS A engine maintainer, I WANT subsystems to self-register, SO THAT modular architecture.
-
-ACCEPTANCE CRITERIA
-
-- [ ] ENG-1.1_AC-1 [event]: WHEN subsystem loads THEN it SHALL register with context
-
-### ENG-2: Resource Management [MUST]
-
-AS A game developer, I WANT automatic resource loading, SO THAT simplified asset management.
-
-ACCEPTANCE CRITERIA
-
-- [ ] ENG-2_AC-1 [event]: WHEN resource requested THEN system SHALL load asynchronously
-- [ ] ENG-2_AC-2 [ubiquitous]: The system SHALL cache loaded resources
-
-DEPENDS ON: ENG-1
-
-## Assumptions
-
-- Target platform supports OpenGL 3.3 or higher
-- Config file uses TOML format with `[section]` syntax
-
-## Constraints
-
-- Must run on Windows, macOS, and Linux
-- CLI options like `--features` and `--remove-features` follow POSIX conventions
-
-## Out of Scope
-
-- Mobile platform support
-- Console platform support
-
-## Change Log
-
-- 1.0.0 (2025-01-10): Initial requirements
-- 1.1.0 (2025-01-15): Added `--preset` CLI option
-</example>
-
-</schema>

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

@@ -1,137 +0,0 @@
-<schema target-files=".awa/tasks/TASK-{CODE}-{feature-name}-{nnn}.md">
-
-```json
-{
-  "description": "Implementation tasks only. Dependency-ordered. Traceable to REQ and DESIGN.",
-  "required": ["feature", "source", "phases", "dependencies", "traceSummary"],
-  "properties": {
-    "feature": { "type": "feature name from REQ" },
-    "source": { "type": "array of source file paths (REQ, DESIGN)" },
-    "phases": { "type": "array", "items": { "$ref": "#/$defs/phase" } },
-    "dependencies": { "type": "array", "items": { "$ref": "#/$defs/dependency" } },
-    "parallelOpportunities": { "type": "array", "items": { "properties": { "phase": {}, "tasks": { "type": "array of task IDs" }, "notes": {} } } },
-    "traceSummary": {
-      "required": ["acCoverage", "propertyCoverage"],
-      "properties": {
-        "acCoverage": { "type": "array", "items": { "properties": { "ac": {}, "task": {}, "test": {} } } },
-        "propertyCoverage": { "type": "array", "items": { "properties": { "property": {}, "test": {} } } },
-        "uncovered": { "type": "array of AC or P IDs" }
-      }
-    }
-  },
-  "$defs": {
-    "phase": {
-      "required": ["name", "tasks"],
-      "properties": {
-        "name": { "type": "phase name" },
-        "type": { "enum": ["setup", "foundation", "requirement", "polish"] },
-        "requirement": { "type": "{CODE}-{n} (only for requirement phases)" },
-        "priority": { "enum": ["must", "should", "could"] },
-        "goal": { "type": "requirement's story.want (only for requirement phases)" },
-        "testCriteria": { "type": "how to verify phase is complete" },
-        "tasks": { "type": "array", "items": { "$ref": "#/$defs/task" } }
-      }
-    },
-    "task": {
-      "required": ["id", "description", "path"],
-      "properties": {
-        "id": { "type": "pattern: T-{CODE}-{nnn} (e.g., T-CFG-001)" },
-        "parallel": { "type": "boolean, true if parallelizable" },
-        "requirement": { "type": "{CODE}-{n} (only in requirement phases)" },
-        "description": { "type": "clear action" },
-        "path": { "type": "target file path" },
-        "implements": { "type": "array of {CODE}-{n}[.{p}]_AC-{m}" },
-        "tests": { "type": "array of {CODE}_P-{n} or {CODE}-{n}[.{p}]_AC-{m}" }
-      }
-    },
-    "dependency": {
-      "required": ["requirement", "dependsOn"],
-      "properties": {
-        "requirement": { "type": "{CODE}-{n}" },
-        "dependsOn": { "type": "array of {CODE}-{n} or empty" },
-        "reason": { "type": "why dependency exists" }
-      }
-    }
-  },
-  "$render": {
-    "template": "# Implementation Tasks\n\nFEATURE: {feature}\nSOURCE: {source}\n\n{phases→'## {name} {[priority]?}\n\n{goal→\"GOAL: {}\"}\n{testCriteria→\"TEST CRITERIA: {}\"}\n\n{tasks→\"- [ ] {id} {[P]?} {[requirement]?} {description} → {path}\n      {implements→\\\"IMPLEMENTS: {}\\\"}\n      {tests→\\\"TESTS: {}\\\"}\"}'}\n\n---\n\n## Dependencies\n{dependencies→'{requirement} → {dependsOn|\"(none)\"} {reason?}'}\n\n## Parallel Opportunities\n{parallelOpportunities→'{phase}: {tasks} {notes?}'}\n\n## Trace Summary\n\n| AC | Task | Test |\n|----|------|------|\n{traceSummary.acCoverage→'| {ac} | {task} | {test} |'}\n\n| Property | Test |\n|----------|------|\n{traceSummary.propertyCoverage→'| {property} | {test} |'}\n\nUNCOVERED: {traceSummary.uncovered|\"(none)\"}",
-    "omit": ["[P] if parallel false/absent", "[requirement] if absent", "[priority] if absent", "GOAL if absent", "TEST CRITERIA if absent", "IMPLEMENTS line if empty", "TESTS line if empty", "reason if absent", "notes if absent"],
-    "prohibited": ["**bold** — use CAPITALS", "tasks without file paths", "IMPLEMENTS/TESTS on setup tasks", "[requirement] labels on setup/foundation/polish phases", "orphan tasks (must trace to AC or P)"],
-    "checkbox": "[ ] always unchecked in generated output"
-  }
-}
-```
-
-<example>
-# Implementation Tasks
-
-FEATURE: Configuration System
-SOURCE: REQ-CFG-config.md, DESIGN-CFG-config.md
-
-## Phase 1: Setup
-
-- [ ] T-CFG-001 Initialize module structure → src/config/
-- [ ] T-CFG-002 [P] Add dependencies (smol-toml) → package.json
-
-## Phase 2: Foundation
-
-- [ ] T-CFG-003 Define Config and RawConfig types → src/config/types.ts
-- [ ] T-CFG-004 Define ConfigError variants → src/config/errors.ts
-
-## Phase 3: Config Loading [MUST]
-
-GOAL: Load and merge configuration from file with defaults
-TEST CRITERIA: Can load valid TOML, missing keys get defaults
-
-- [ ] T-CFG-010 [CFG-1] Implement load function → src/config/loader.ts
-  IMPLEMENTS: CFG-1_AC-1
-- [ ] T-CFG-011 [CFG-1] Implement merge function → src/config/loader.ts
-  IMPLEMENTS: CFG-1_AC-2
-- [ ] T-CFG-012 [P] [CFG-1] Property test for default preservation → tests/config/loader.test.ts
-  TESTS: CFG_P-1
-- [ ] T-CFG-013 [P] [CFG-1] Test load from valid path → tests/config/loader.test.ts
-  TESTS: CFG-1_AC-1
-
-## Phase 4: Config Validation [SHOULD]
-
-GOAL: Validate loaded config against schema
-TEST CRITERIA: Invalid config rejected with clear error
-
-- [ ] T-CFG-020 [CFG-2] Implement validate function → src/config/validator.ts
-  IMPLEMENTS: CFG-2_AC-1
-- [ ] T-CFG-021 [P] [CFG-2] Test schema validation → tests/config/validator.test.ts
-  TESTS: CFG-2_AC-1
-
-## Phase 5: Polish
-
-- [ ] T-CFG-030 Integration test: load → validate → use → tests/config/integration.test.ts
-  TESTS: CFG-1_AC-1, CFG-2_AC-1
-
----
-
-## Dependencies
-
-CFG-1 → (none)
-CFG-2 → CFG-1 (validates loaded config)
-
-## Parallel Opportunities
-
-Phase 3: T-CFG-012, T-CFG-013 can run parallel after T-CFG-011
-Phase 4: T-CFG-021 can run parallel with T-CFG-020
-
-## Trace Summary
-
-| AC | Task | Test |
-|----|------|------|
-| CFG-1_AC-1 | T-CFG-010 | T-CFG-013 |
-| CFG-1_AC-2 | T-CFG-011 | T-CFG-012 |
-| CFG-2_AC-1 | T-CFG-020 | T-CFG-021 |
-
-| Property | Test |
-|----------|------|
-| CFG_P-1 | T-CFG-012 |
-
-UNCOVERED: (none)
-</example>
-
-</schema>

package/templates/awa/.claude/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.codex/prompts/awa-validate-alignment.md

@@ -1,3 +0,0 @@
-<% if (it.features.includes('codex')) { %>
-<%~ include('_partials/_cmd.awa-validate-alignment.md', it) %>
-<% } %>

package/templates/awa/.cursor/rules/awa-validate-alignment.md

@@ -1,8 +0,0 @@
-<% if (it.features.includes('cursor')) { %>
----
-description: Validate alignment of source with target
-alwaysApply: false
----
-
-<%~ include('_partials/awa.validate-alignment.md', it) %>
-<% } %>

package/templates/awa/.gemini/commands/awa-validate-alignment.md

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

package/templates/awa/.gemini/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.github/prompts/awa.validate-alignment.prompt.md

@@ -1,8 +0,0 @@
-<% if (it.features.includes('copilot')) { %>
----
-description: Validate alignment of source with target (check source matches target, and if not list differences)
-argument-hint: "<source> [<target>]"
----
-
-<%~ include('_partials/awa.validate-alignment.md', it) %>
-<% } %>

package/templates/awa/.github/skills/awa-validate-alignment/SKILL.md

@@ -1,8 +0,0 @@
-<% if (it.features.includes('copilot')) { %>
----
-name: awa-validate-alignment
-description: Validate alignment of source with target. Use this when asked to validate, check, or verify alignment between artifacts.
----
-
-<%~ include('_partials/awa.validate-alignment.md', it) %>
-<% } %>

package/templates/awa/.kilocode/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.kilocode/workflows/awa-validate-alignment.md

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

package/templates/awa/.opencode/commands/awa-validate-alignment.md

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

package/templates/awa/.opencode/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.qwen/commands/awa-validate-alignment.md

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

package/templates/awa/.qwen/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.roo/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/.windsurf/skills/awa-validate-alignment/SKILL.md

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

package/templates/awa/_partials/_skill.awa-validate-alignment.md

@@ -1,6 +0,0 @@
----
-name: awa-validate-alignment
-description: Validate alignment of source with target. Use this when asked to validate, check, or verify alignment between artifacts.
----
-
-<%~ include('awa.validate-alignment.md', it) %>