@ncoderz/awa 1.7.1 → 1.8.0

package/templates/awa/_tests/claude/.claude/skills/awa-code/SKILL.md

@@ -0,0 +1,179 @@
+---
+name: awa-code
+description: Implement code and tests based on architecture, requirements, and design (or a set of tasks). Use this when asked to implement features, write code, or create tests.
+---
+
+# Implement Code and Tests from Architecture, Requirements, Design, and (optional) Tasks
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<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/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" />
+<file type="tasks" path=".awa/tasks/TASK-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="code" required="if relevant" />
+
+## Action
+
+Implement code and tests based on architecture, requirements, and design (tasks optional) as specified in the instruction above, following awa conventions.
+
+## Traceability Markers
+
+You MUST add these markers to create explicit traces:
+
+```
+// @awa-component: {CODE}-{ComponentName}
+```
+Place at the top of each file/module that implements a design component.
+
+```
+// @awa-impl: {CODE}-{n}[.{p}]_AC-{m}
+```
+Place above code that satisfies an acceptance criterion. Multiple markers allowed per block.
+
+```
+// @awa-test: {CODE}_P-{n}
+// @awa-test: {CODE}-{n}[.{p}]_AC-{m}
+```
+Place above tests. Use P- for property-based tests, AC- for direct acceptance tests.
+
+## Implementation Process
+
+1. PARSE DESIGN
+  - Identify components and their interfaces
+  - Note IMPLEMENTS references (which ACs each component covers)
+  - Note properties ({CODE}_P-{n}) and what they VALIDATE
+
+2. PARSE REQ
+  - Understand acceptance criteria being implemented
+  - Note criterion types (event, ubiquitous, conditional, etc.)
+
+3. IF TASKS PROVIDED
+  - Follow task order strictly
+  - Implement one task at a time
+  - Update TASK file checkmark, and report completion of each task before proceeding to the next
+
+4. IF NO TASKS
+  - Implement components in dependency order
+  - Start with bootstrapping, then types/interfaces, then core logic, then entry points
+
+5. FOR EACH COMPONENT
+  - Add @awa-component marker at file/module top
+  - Implement interface as specified in DESIGN
+  - Add @awa-impl marker above code satisfying each AC
+  - One AC may require multiple @awa-impl markers across files
+
+6. FOR EACH TEST
+  - Property tests (@awa-test: {CODE}_P-{n}): Use property-based testing framework
+  - Acceptance tests (@awa-test: {CODE}-{n}[.{p}]_AC-{m}): Use example-based assertions
+  - A single test may verify multiple ACs or properties
+
+7. UPDATE DOCUMENTATION
+  - If user-facing behavior changed: update user docs
+  - If CLI commands or options changed: update CLI reference docs
+  - If project structure changed: update ARCHITECTURE.md
+  - If no user-facing changes: skip this step
+
+## Outputs
+
+- source code files with appropriate markers
+- test files with appropriate markers
+- associated project configuration files if needed
+- updated documentation if necessary
+
+## Constraints
+
+- Never implement without a corresponding DESIGN component
+- Never add @awa-impl without understanding the AC's criterion type
+- Prefer one @awa-component per file; split if file covers multiple components
+- Keep @awa-impl markers close to the implementing code, not at file top
+- If AC cannot be fully satisfied, add marker with comment: `// @awa-impl: {CODE}-{n}[.{p}]_AC-{m} (partial: reason)`
+- If PLAN task is blocked, report blocker and await instruction
+
+## Example
+
+Given:
+- CFG-1: Config Loading with CFG-1_AC-1 (load from path), CFG-1_AC-2 (merge with defaults)
+- DESIGN component CFG-ConfigLoader with IMPLEMENTS: CFG-1_AC-1, CFG-1_AC-2
+- DESIGN property CFG_P-1 [Default Preservation] VALIDATES: CFG-1_AC-2
+
+Output:
+
+```typescript
+// FILE: src/config/loader.ts
+
+// @awa-component: CFG-ConfigLoader
+
+import { Config, RawConfig } from './types';
+import { defaults } from './defaults';
+
+// @awa-impl: CFG-1_AC-1
+export async function load(path: string): Promise {
+  const content = await fs.readFile(path, 'utf8');
+  return parse(content);
+}
+
+// @awa-impl: CFG-1_AC-2
+export function merge(raw: RawConfig): Config {
+  return { ...defaults, ...raw };
+}
+```
+
+```typescript
+// FILE: tests/config/loader.test.ts
+
+import * as fc from 'fast-check';
+
+// @awa-test: CFG_P-1
+test.prop([fc.object()])('preserves defaults for missing keys', (partial) => {
+  const result = merge(partial);
+  for (const [key, value] of Object.entries(defaults)) {
+    if (!(key in partial)) {
+      expect(result[key]).toBe(value);
+    }
+  }
+});
+
+// @awa-test: CFG-1_AC-1
+test('loads config from valid path', async () => {
+  const config = await load('fixtures/valid.toml');
+  expect(config).toBeDefined();
+});
+```
+
+## Rules
+
+You SHALL write code at the level of a technical lead.
+You SHALL consider edge cases and error handling.
+You SHALL use KISS, and YAGNI principles. Do not create more than requested.
+You SHALL write tests to cover the requirements and success criteria. If no tests exist for the written code, you MUST create them.
+You SHALL actively research existing code to apply the DRY principle.
+You SHALL consider edge cases, UX, technical constraints, success criteria.
+You MUST NOT add features or functionality beyond what is specified or requested.
+You SHALL use any tools you need to help write and test code (e.g. MCP tools for result visualization).
+You MUST add traceability markers (`@awa-component`, `@awa-impl`, `@awa-test`) to all code and tests.
+You MUST ensure every feature implementation traces to at least one acceptance criterion.
+You MUST ensure every test file traces to at least one design property.
+You MUST run `awa check` after implementation to verify all traceability markers resolve to spec IDs and no acceptance criteria are left uncovered.
+You SHALL update user-facing documentation when implementation changes user-facing behavior, CLI, API, or configuration.
+You SHALL clarify open points with user.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-design/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: awa-design
+description: Create or update design documents. Use this when asked to create, update or modify feature designs.
+---
+
+# Create or Update Design(s)
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+ <read path=".awa/.agent/schemas/DESIGN.schema.yaml" required="true" error="on not found" />
+ <read path=".awa/.agent/schemas/REQ.schema.yaml" optional="true" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<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/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" />
+<file type="code" required="if reverse workflow" />
+
+## Action
+
+Update or create the design document(s) as specified in the instruction above, following awa conventions.
+
+If deriving from existing code (reverse workflow), analyze the codebase to extract component structure, interfaces, data models, and design patterns.
+
+## Outputs
+
+<file path=".awa/specs/DESIGN-{CODE}-{feature-name}.md" />
+<file path=".awa/specs/API-{CODE}-{api-name}.tsp" />
+
+## 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.
+You SHALL define component interfaces, data models, and error handling strategies.
+You SHALL identify existing requirements to update, or new requirements to create.
+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 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.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-documentation/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: awa-documentation
+description: Create or update project documentation (README.md and /docs). Use this when asked to write, update or improve documentation.
+---
+
+# Create or Update Documentation
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+ <read path=".awa/.agent/schemas/README.schema.yaml" required="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
+<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="readme" path="README.md" required="if exists" />
+<file type="docs" path="docs/*.md" required="if exists and relevant" />
+
+## Action
+
+Update or create documentation as specified in the instruction above, following awa conventions.
+
+## Documentation Structure Example
+
+```
+README.md              # Project entry point (user-facing)
+docs/
+├── {topic}.md         # Documentation on a specific topic
+├── getting-started.md # Quick start guide
+├── configuration.md   # Configuration reference
+├── cli-reference.md   # CLI command reference (if CLI project)
+├── api.md             # API reference (if library)
+├── templates.md       # Template authoring (if template-based)
+├── architecture.md    # Public architecture overview (optional)
+└── contributing.md    # Contribution guidelines (or CONTRIBUTING.md at root)
+```
+
+## Documentation Principles
+
+1. README.md is the entry point
+   - User-facing, not developer-facing
+   - Brief and scannable
+   - Links to /docs for details
+   - Shows quick start, not comprehensive guide
+
+2. /docs contains detailed documentation
+   - Each file covers one topic
+   - Reference style for commands/APIs
+   - Tutorial style for guides
+   - Keep files under the specified line-limit; split if larger
+
+3. Derive from specifications
+   - Do not duplicate; summarize and link
+
+4. Keep synchronized
+   - Update docs when specs change
+   - Remove docs for deprecated features
+
+## Output Files
+
+<file path="README.md" />
+<file path="docs/{topic}.md" />
+
+## Rules
+
+You SHALL write documentation for end users, not internal developers.
+You SHALL keep README.md concise and link to /docs for details.
+You SHALL derive documentation content from architecture and design specs.
+You SHALL NOT duplicate specification content; summarize and reference.
+You SHALL ensure code examples are accurate and runnable.
+You SHALL use consistent terminology matching the glossary in specs.
+You SHALL organize /docs by topic, not by component.
+You SHALL include practical examples for each feature documented.
+You SHOULD update documentation when related specifications change.
+You SHOULD include troubleshooting sections for common issues.
+You SHALL clarify open points with user.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-examples/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: awa-examples
+description: Create or update usage examples for a feature. Use this when asked to provide detailed code examples, CLI demonstrations, or configuration samples.
+---
+
+# Create or Update Usage Examples
+
+## Bootstrap
+
+<tool name="read_file">
+ <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/EXAMPLE.schema.yaml" required="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
+<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/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if updating" />
+<file type="code" required="if relevant" />
+
+## Action
+
+Create or update concrete usage examples for a feature as specified in the instruction above, following awa conventions.
+
+If deriving from existing code (reverse workflow), extract representative usage patterns, CLI invocations, and configuration samples.
+
+## Outputs
+
+<file path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" />
+
+## Rules
+
+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 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.
+You SHALL support reverse workflow: extracting examples from existing code when requested.
+You SHALL clarify open points with user.
+You MAY include prerequisites, expected output, and notes for each example.
+You MAY create examples proactively when detailed demonstrations would aid understanding.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-feature/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: awa-feature
+description: Create or update feature context documents. Use this when asked to describe a feature, explain motivation, or provide non-normative context.
+---
+
+# Create or Update Feature Context
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+ <read path=".awa/.agent/schemas/FEAT.schema.yaml" required="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
+<file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="if updating" />
+<file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" />
+<file type="code" required="if reverse workflow" />
+
+## 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.
+
+## Outputs
+
+<file path=".awa/specs/FEAT-{CODE}-{feature-name}.md" />
+
+## 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 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.
+You MAY include diagrams, background, and non-normative notes as needed.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-plan/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: awa-plan
+description: Create or update ad-hoc plan documents. Use this when asked to create plans, break down work, or organize tasks, but not when specifically asked to create tasks from requirements and design documents.
+---
+
+# Create or Update Plan(s)
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+ <read path=".awa/.agent/schemas/PLAN.schema.yaml" required="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<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/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" />
+<file type="code_and_tests" path="various" required="if relevant" />
+
+## Action
+
+Update or create the ad-hoc plan document(s) as specified in the instruction above, following awa conventions.
+
+## Outputs
+
+<file path=".awa/plans/PLAN-{nnn}-{plan-name}.md" />
+
+## Rules
+
+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-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.
+You SHALL clarify open points with user.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-refactor/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: awa-refactor
+description: Refactor code or docs while preserving behavior, meaning, and traceability. Use this when asked to refactor, restructure, or improve code quality.
+---
+
+# Refactor Code
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
+<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" />
+<file type="tasks" path=".awa/tasks/TASK-{CODE}-{feature-name}-{nnn}.md" required="if relevant" />
+<file type="code" required="if relevant" />
+
+## Action
+
+Refactor the specified cod or docs as instructed, following awa conventions.
+
+## Outputs
+
+- Refactored source code files with preserved markers
+- Updated test files if structure changed
+- Refactored documentation
+
+## Rules
+
+You SHALL preserve existing behavior unless explicitly asked to change it.
+You SHALL maintain all traceability markers (@awa-component, @awa-impl, @awa-test).
+You SHALL run `awa check` after refactoring to verify all traceability markers are preserved and still resolve correctly.
+You SHALL ensure tests pass before and after refactoring.
+You SHALL make incremental changes, not wholesale rewrites.
+You SHALL NOT change public interfaces without explicit approval.
+You SHALL update user-facing documentation when implementation changes user-facing behavior, CLI, API, or configuration.
+You SHALL clarify scope and risks with user before major refactors.
+You MAY use todos and tools as needed.

package/templates/awa/_tests/claude/.claude/skills/awa-requirements/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: awa-requirements
+description: Create or update requirements documents. Use this when asked to create, update or modify requirements.
+---
+
+# Create or Update Requirements
+
+## Bootstrap
+
+<tool name="read_file">
+ <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="true" error="on not found" />
+ <read path=".awa/.agent/schemas/REQ.schema.yaml" required="true" error="on not found" />
+</tool>
+
+## User Input
+
+```text
+${input}
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Inputs
+
+<file type="architecture" path=".awa/specs/ARCHITECTURE.md" />
+<file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="true" />
+<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="code" required="if reverse workflow" />
+
+## Action
+
+Create or update the requirements document(s) as specified in the instruction above, following awa conventions.
+Consider existing specifications before making changes.
+
+If deriving from existing code (reverse workflow), analyze the codebase to extract implicit requirements, acceptance criteria, and behavioral expectations.
+
+## Outputs
+
+<file path=".awa/specs/REQ-{CODE}-{feature-name}.md" />
+
+## Rules
+
+You SHALL ensure the {CODE} matches the corresponding FEAT {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 read the corresponding FEAT document before writing requirements.
+You SHALL solidify requirements with respect to architecture, feature context, and existing requirements.
+You SHALL create set of requirements in EARS format (INCOSE-compliant) based on the feature context.
+You SHALL identify existing requirements to update, or new requirements to create.
+You SHALL consider edge cases, UX, technical constraints, success criteria.
+You SHOULD focus on requirements which will later be turned into a design.
+You SHOULD keep requirements at a manageable level of detail.
+You SHALL ensure requirement IDs and AC IDs follow the format defined in the traceability chain (e.g. `{CODE}-{n}`, `{CODE}-{n}_AC-{m}`, `{CODE}-{n}.{p}_AC-{m}`).
+You SHALL support reverse workflow: deriving requirements from existing code when requested.
+You SHALL clarify open points with user.
+You MAY use todos and tools as needed.