@mytechtoday/augment-extensions 0.7.0 → 1.2.0

package/AGENTS.md

@@ -1,232 +1,265 @@
-# Augment Extensions - AI Agent Integration
-
-This repository provides extension modules for Augment Code AI that exceed the standard `.augment/` character limit.
-
-## For AI Agents
-
-### Discovery
-
-You can discover and use extension modules through the `augx` CLI:
-
-```bash
-# List all available modules
-augx list
-
-# Show module details
-augx show <module-name>
-
-# Search for modules
-augx search <keyword>
-```
-
-### Usage in Projects
-
-When working on a project that has Augment Extensions linked:
-
-1. **Check linked modules**: `augx list --linked`
-2. **View module content**: `augx show <module-name>`
-3. **Apply module rules**: Follow the guidelines in the module's rules/ directory
-
-### Module Structure
-
-Each module contains:
-- `module.json` - Metadata and configuration
-- `rules/` - Markdown files with detailed guidelines
-- `examples/` - Code examples demonstrating best practices
-- `README.md` - Module overview
-
-### Integration Workflow
-
-1. Human initializes: `augx init`
-2. Human links modules: `augx link coding-standards/typescript`
-3. AI agent queries: `augx show typescript-standards`
-4. AI agent applies rules from module content
-
-### CLI Commands Reference
-
-- `augx list` - List all available modules
-- `augx list --linked` - List modules linked to current project
-- `augx show <module>` - Display module content
-- `augx search <term>` - Search for modules
-- `augx update` - Update all linked modules
-- `augx version` - Show CLI version
-
-## Module Types
-
-1. **coding-standards** - Language/framework specific standards
-2. **domain-rules** - Domain-specific guidelines (web, API, security, etc.)
-3. **workflows** - Process and methodology integration (OpenSpec, Beads, etc.)
-4. **examples** - Extensive code examples and patterns
-
-## Character Limit Context
-
-- Standard `.augment/` limit: ~49,400 characters
-- Extension modules: No limit (stored separately)
-- Modules are loaded on-demand when relevant to current task
-
-## Best Practices for AI Agents
-
-1. **Query before applying**: Always check module content before applying rules
-2. **Respect versions**: Use pinned versions for consistency
-3. **Combine modules**: Multiple modules can be active simultaneously
-4. **Report issues**: If module content conflicts, notify the human
-
-## Example Usage
-
-```bash
-# AI agent working on TypeScript project
-$ augx list --linked
-typescript-standards (v1.0.0)
-react-patterns (v2.1.0)
-
-$ augx show typescript-standards
-# Returns full module content including all rules and examples
-```
-
----
-
-## OpenSpec Integration
-
-This repository uses **OpenSpec** for spec-driven development.
-
-### OpenSpec Workflow
-
-1. **Draft Change Proposal**: Create `openspec/changes/[change-name]/proposal.md`
-2. **Review & Align**: Create spec deltas in `openspec/changes/[change-name]/specs/`
-3. **Implement Tasks**: Create `openspec/changes/[change-name]/tasks.md` and implement
-4. **Archive**: Move completed change to `openspec/archive/[change-name]/`
-
-### OpenSpec Files
-
-- `openspec/project-context.md` - Project overview and architecture
-- `openspec/specs/` - Source of truth specifications
-- `openspec/changes/` - Proposed changes (deltas)
-- `openspec/archive/` - Completed changes
-
-### For AI Agents
-
-When making architectural changes:
-1. Create a change proposal in `openspec/changes/`
-2. Define spec deltas (ADDED/MODIFIED/REMOVED sections)
-3. Break down into tasks
-4. Implement and archive when complete
-
-**Learn More**: See `augment-extensions/workflows/openspec/` for comprehensive workflow documentation.
-
----
-
-## Beads Integration
-
-This repository uses **Beads** for task tracking and memory.
-
-### Beads Workflow
-
-1. **Create Task**: Append to `.beads/issues.jsonl` with unique hash-based ID
-2. **Add Dependencies**: Use `blocks` and `blocked_by` fields
-3. **Find Ready Tasks**: Tasks with no open blockers
-4. **Work on Task**: Update status to `in-progress`, add comments
-5. **Close Task**: Update status to `closed`
-
-### Beads Files
-
-- `.beads/issues.jsonl` - All issues (append-only JSONL log)
-- `.beads/config.json` - Beads configuration
-- `.beads/cache.db` - SQLite cache (gitignored, CLI only)
-
-### For AI Agents
-
-When tracking work:
-1. Create tasks by appending JSON to `.beads/issues.jsonl`
-2. Use hash-based IDs with **"bd-" prefix**: `bd-<hash>` (e.g., `bd-a1b2`)
-   - All issue IDs MUST use "bd-" prefix (see `openspec/specs/beads/naming-convention.md`)
-   - Valid formats: `bd-<hash>`, `bd-<name>`, `bd-<hash>.<number>`
-3. Track dependencies with `blocks`/`blocked_by` fields
-4. Find ready tasks (status: "open", no blockers)
-5. Update status and add comments as work progresses
-
-**Task States**: `open`, `in-progress`, `blocked`, `closed`
-
-**Naming Convention**: All issue IDs MUST use "bd-" prefix. See `openspec/specs/beads/naming-convention.md` for complete specification.
-
-**Learn More**: See `augment-extensions/workflows/beads/` for comprehensive workflow documentation.
-
----
-
-## Coordination System
-
-This repository uses a **coordination manifest** (`.augment/coordination.json`) to harmonize OpenSpec, Beads, and `.augment/` rules.
-
-### How It Works
-
-The coordination manifest tracks relationships between:
-- **Specs** (OpenSpec) - What needs to be built
-- **Tasks** (Beads) - How it's being built
-- **Rules** (`.augment/`) - Guidelines for building
-- **Files** - What was built
-
-### For AI Agents
-
-**Before starting work**:
-1. Check `.augment/coordination.json` for active specs
-2. Find related tasks for the spec you're implementing
-3. Load applicable rules for your task
-4. Identify which files are affected
-
-**While working**:
-1. Track file creation/modification with task IDs
-2. Update coordination manifest when creating files
-3. Reference specs and rules in task comments
-
-**Query Examples**:
-
-```javascript
-// Get all active specs
-const coord = require('./.augment/coordination.json');
-const activeSpecs = Object.entries(coord.specs)
-  .filter(([id, spec]) => spec.status === 'active');
-
-// Get tasks for a spec
-const tasks = coord.specs['testing/functional-tests'].relatedTasks;
-
-// Get rules for a task
-const rules = coord.tasks['bd-xyz'].relatedRules;
-
-// Get specs governing a file
-const specsForFile = Object.entries(coord.specs)
-  .filter(([id, spec]) =>
-    spec.affectedFiles.some(pattern => filePath.match(pattern))
-  );
-```
-
-**Learn More**: See `.augment/rules/coordination-system.md` for detailed documentation.
-
----
-
-**Note**: This is a meta-repository for extending Augment Code AI. The actual project-specific `.augment/` folder remains in individual projects.
-
-
-## Landing the Plane (Session Completion)
-
-**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
-
-**MANDATORY WORKFLOW:**
-
-1. **File issues for remaining work** - Create issues for anything that needs follow-up
-2. **Run quality gates** (if code changed) - Tests, linters, builds
-3. **Update issue status** - Close finished work, update in-progress items
-4. **PUSH TO REMOTE** - This is MANDATORY:
-   ```bash
-   git pull --rebase
-   bd sync
-   git push
-   git status  # MUST show "up to date with origin"
-   ```
-5. **Clean up** - Clear stashes, prune remote branches
-6. **Verify** - All changes committed AND pushed
-7. **Hand off** - Provide context for next session
-
-**CRITICAL RULES:**
-- Work is NOT complete until `git push` succeeds
-- NEVER stop before pushing - that leaves work stranded locally
-- NEVER say "ready to push when you are" - YOU must push
-- If push fails, resolve and retry until it succeeds
+# Augment Extensions - AI Agent Integration
+
+This repository provides extension modules for Augment Code AI that exceed the standard `.augment/` character limit.
+
+## For AI Agents
+
+### Discovery
+
+You can discover and use extension modules through the `augx` CLI:
+
+```bash
+# List all available modules
+augx list
+
+# Show module details
+augx show <module-name>
+
+# Search for modules
+augx search <keyword>
+```
+
+### Usage in Projects
+
+When working on a project that has Augment Extensions linked:
+
+1. **Check linked modules**: `augx list --linked`
+2. **View module content**: `augx show <module-name>`
+3. **Apply module rules**: Follow the guidelines in the module's rules/ directory
+
+### Module Structure
+
+Each module contains:
+- `module.json` - Metadata and configuration
+- `rules/` - Markdown files with detailed guidelines
+- `examples/` - Code examples demonstrating best practices
+- `README.md` - Module overview
+
+### Integration Workflow
+
+1. Human initializes: `augx init`
+2. Human links modules: `augx link coding-standards/typescript`
+3. AI agent queries: `augx show typescript-standards`
+4. AI agent applies rules from module content
+
+### CLI Commands Reference
+
+- `augx list` - List all available modules
+- `augx list --linked` - List modules linked to current project
+- `augx show <module>` - Display module content
+- `augx show linked` - Show all linked modules
+- `augx show all` - Show all available modules
+- `augx search <term>` - Search for modules
+- `augx update` - Update all linked modules
+- `augx version` - Show CLI version
+
+### Command Help Reference
+
+When `augx init` is run, the CLI automatically generates `.augment/COMMAND_HELP.md` containing comprehensive help documentation for all detected workflow tools (Beads, OpenSpec, Augx).
+
+**For AI Agents:**
+
+1. **Check for help reference**: Look for `.augment/COMMAND_HELP.md` in the project
+2. **Use for command discovery**: Reference the file to learn available commands and their syntax
+3. **Generate accurate commands**: Use the help text to construct correct command invocations
+4. **Understand tool capabilities**: Learn what each tool can do without executing commands
+
+**Example workflow:**
+
+```bash
+# AI agent discovers available commands
+cat .augment/COMMAND_HELP.md
+
+# AI agent learns Beads commands
+# Sees: "bd create <title> - Create a new issue"
+
+# AI agent generates correct command
+bd create "Implement feature X" -p 1
+```
+
+**Benefits:**
+- **No trial-and-error**: AI agents know exact command syntax before execution
+- **Always current**: Regenerated on `augx init` to reflect latest tool versions
+- **Comprehensive**: Includes main commands and all subcommands (up to 3 levels deep)
+- **Multi-tool**: Single reference for all workflow tools in the project
+
+## Module Types
+
+1. **coding-standards** - Language/framework specific standards
+2. **domain-rules** - Domain-specific guidelines (web, API, security, etc.)
+3. **workflows** - Process and methodology integration (OpenSpec, Beads, etc.)
+4. **examples** - Extensive code examples and patterns
+
+## Character Limit Context
+
+- Standard `.augment/` limit: ~49,400 characters
+- Extension modules: No limit (stored separately)
+- Modules are loaded on-demand when relevant to current task
+
+## Best Practices for AI Agents
+
+1. **Query before applying**: Always check module content before applying rules
+2. **Respect versions**: Use pinned versions for consistency
+3. **Combine modules**: Multiple modules can be active simultaneously
+4. **Report issues**: If module content conflicts, notify the human
+
+## Example Usage
+
+```bash
+# AI agent working on TypeScript project
+$ augx list --linked
+typescript-standards (v1.0.0)
+react-patterns (v2.1.0)
+
+$ augx show typescript-standards
+# Returns full module content including all rules and examples
+```
+
+---
+
+## OpenSpec Integration
+
+This repository uses **OpenSpec** for spec-driven development.
+
+### OpenSpec Workflow
+
+1. **Draft Change Proposal**: Create `openspec/changes/[change-name]/proposal.md`
+2. **Review & Align**: Create spec deltas in `openspec/changes/[change-name]/specs/`
+3. **Implement Tasks**: Create `openspec/changes/[change-name]/tasks.md` and implement
+4. **Archive**: Move completed change to `openspec/archive/[change-name]/`
+
+### OpenSpec Files
+
+- `openspec/project-context.md` - Project overview and architecture
+- `openspec/specs/` - Source of truth specifications
+- `openspec/changes/` - Proposed changes (deltas)
+- `openspec/archive/` - Completed changes
+
+### For AI Agents
+
+When making architectural changes:
+1. Create a change proposal in `openspec/changes/`
+2. Define spec deltas (ADDED/MODIFIED/REMOVED sections)
+3. Break down into tasks
+4. Implement and archive when complete
+
+**Learn More**: See `augment-extensions/workflows/openspec/` for comprehensive workflow documentation.
+
+---
+
+## Beads Integration
+
+This repository uses **Beads** for task tracking and memory.
+Use 'bd' for task tracking
+
+### Beads Workflow
+
+1. **Create Task**: Append to `.beads/issues.jsonl` with unique hash-based ID
+2. **Add Dependencies**: Use `blocks` and `blocked_by` fields
+3. **Find Ready Tasks**: Tasks with no open blockers
+4. **Work on Task**: Update status to `in-progress`, add comments
+5. **Close Task**: Update status to `closed`
+
+### Beads Files
+
+- `.beads/issues.jsonl` - All issues (append-only JSONL log)
+- `.beads/config.json` - Beads configuration
+- `.beads/cache.db` - SQLite cache (gitignored, CLI only)
+
+### For AI Agents
+
+When tracking work:
+1. Create tasks by appending JSON to `.beads/issues.jsonl`
+2. Use hash-based IDs with **"bd-" prefix**: `bd-<hash>` (e.g., `bd-a1b2`)
+   - All issue IDs MUST use "bd-" prefix (see `openspec/specs/beads/naming-convention.md`)
+   - Valid formats: `bd-<hash>`, `bd-<name>`, `bd-<hash>.<number>`
+3. Track dependencies with `blocks`/`blocked_by` fields
+4. Find ready tasks (status: "open", no blockers)
+5. Update status and add comments as work progresses
+
+**Task States**: `open`, `in_progress`, `blocked`, `closed`
+
+**Naming Convention**: All issue IDs MUST use "bd-" prefix. See `openspec/specs/beads/naming-convention.md` for complete specification.
+
+**Learn More**: See `augment-extensions/workflows/beads/` for comprehensive workflow documentation.
+
+---
+
+## Coordination System
+
+This repository uses a **coordination manifest** (`.augment/coordination.json`) to harmonize OpenSpec, Beads, and `.augment/` rules.
+
+### How It Works
+
+The coordination manifest tracks relationships between:
+- **Specs** (OpenSpec) - What needs to be built
+- **Tasks** (Beads) - How it's being built
+- **Rules** (`.augment/`) - Guidelines for building
+- **Files** - What was built
+
+### For AI Agents
+
+**Before starting work**:
+1. Check `.augment/coordination.json` for active specs
+2. Find related tasks for the spec you're implementing
+3. Load applicable rules for your task
+4. Identify which files are affected
+
+**While working**:
+1. Track file creation/modification with task IDs
+2. Update coordination manifest when creating files
+3. Reference specs and rules in task comments
+
+**Query Examples**:
+
+```javascript
+// Get all active specs
+const coord = require('./.augment/coordination.json');
+const activeSpecs = Object.entries(coord.specs)
+  .filter(([id, spec]) => spec.status === 'active');
+
+// Get tasks for a spec
+const tasks = coord.specs['testing/functional-tests'].relatedTasks;
+
+// Get rules for a task
+const rules = coord.tasks['bd-xyz'].relatedRules;
+
+// Get specs governing a file
+const specsForFile = Object.entries(coord.specs)
+  .filter(([id, spec]) =>
+    spec.affectedFiles.some(pattern => filePath.match(pattern))
+  );
+```
+
+**Learn More**: See `.augment/rules/coordination-system.md` for detailed documentation.
+
+---
+
+**Note**: This is a meta-repository for extending Augment Code AI. The actual project-specific `.augment/` folder remains in individual projects.
+
+
+## Landing the Plane (Session Completion)
+
+**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
+
+**MANDATORY WORKFLOW:**
+
+1. **File issues for remaining work** - Create issues for anything that needs follow-up
+2. **Run quality gates** (if code changed) - Tests, linters, builds
+3. **Update issue status** - Close finished work, update in-progress items
+4. **PUSH TO REMOTE** - This is MANDATORY:
+   ```bash
+   git pull --rebase
+   bd sync
+   git push
+   git status  # MUST show "up to date with origin"
+   ```
+5. **Clean up** - Clear stashes, prune remote branches
+6. **Verify** - All changes committed AND pushed
+7. **Hand off** - Provide context for next session
+
+**CRITICAL RULES:**
+- Work is NOT complete until `git push` succeeds
+- NEVER stop before pushing - that leaves work stranded locally
+- NEVER say "ready to push when you are" - YOU must push
+- If push fails, resolve and retry until it succeeds