agile-context-engineering 0.2.2 → 0.3.0

package/commands/ace/help.md

@@ -1,93 +1,93 @@
----
-name: ace:help
-description: Check project initialization status and suggest next steps
-argument-hint: ""
-allowed-tools:
-  - Read
-  - Bash
-  - Write
-  - AskUserQuestion
----
-
-```xml
-<command>
-
-    <execution-time>
-        <runs-after>
-            <trigger>At any time — to check which ACE documents exist and what to do next</trigger>
-            <trigger>At the start of a new project — to see the initialization checklist</trigger>
-        </runs-after>
-        <use-when>
-            <condition>Starting a new project and want to see what needs to be set up</condition>
-            <condition>Returning to a project and want to check initialization status</condition>
-            <condition>Unsure which ACE command to run next</condition>
-        </use-when>
-    </execution-time>
-
-    <input>
-        <flags>
-        </flags>
-
-        <parameters>
-            <required>
-            </required>
-
-            <optional>
-            </optional>
-        </parameters>
-    </input>
-
-    <execution-context>
-        <help-workflow>@~/.claude/agile-context-engineering/workflows/help.xml</help-workflow>
-        <questioning>@~/.claude/agile-context-engineering/utils/questioning.xml</questioning>
-        <ui-formatting>@~/.claude/agile-context-engineering/utils/ui-formatting.md</ui-formatting>
-    </execution-context>
-
-    <output>
-        <objective>
-            Detect which ACE documents exist (product vision, system architecture, system structure,
-            coding standards, testing framework). Display a status dashboard showing what's done
-            and what's missing. Suggest the next command to run based on gaps.
-        </objective>
-
-        <artifacts>
-            - .ace/settings.json (created on first run if missing)
-        </artifacts>
-    </output>
-
-    <process>
-        Execute the help workflow from
-        `@~/.claude/agile-context-engineering/workflows/help.xml` end-to-end.
-        This is a lightweight state-check and routing workflow.
-
-        CRITICAL MANDATORY STEP — DO NOT SKIP:
-        Before displaying the status dashboard, you MUST run:
-        ```bash
-        node ~/.claude/agile-context-engineering/src/ace-tools.js sync-agent-teams --raw
-        ```
-        Then you MUST use `AskUserQuestion` to ask the user whether they want to
-        enable or disable Claude Code Agent Teams (experimental feature).
-        This step is NOT optional. You MUST present this question every time.
-
-        When the user chooses to enable or disable Agent Teams, you MUST run the
-        bash command — NEVER directly edit .ace/settings.json or .claude/settings.json:
-        ```bash
-        node ~/.claude/agile-context-engineering/src/ace-tools.js write-agent-teams true
-        ```
-        or
-        ```bash
-        node ~/.claude/agile-context-engineering/src/ace-tools.js write-agent-teams false
-        ```
-        The write-agent-teams command updates BOTH .ace/settings.json AND .claude/settings.json.
-        Direct file edits will cause the two files to go out of sync.
-    </process>
-
-    <next-steps>
-        **Specialized commands for each document:**
-        - `/ace:plan-product-vision` — Create or update the product vision
-        - `/ace:map-system` — Map codebase structure, architecture, and testing framework
-        - `/ace:init-coding-standards` — Generate tailored coding standards
-    </next-steps>
-
-</command>
-```
+---
+name: ace:help
+description: Check project initialization status and suggest next steps
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Bash
+  - Write
+  - AskUserQuestion
+---
+
+```xml
+<command>
+
+    <execution-time>
+        <runs-after>
+            <trigger>At any time — to check which ACE documents exist and what to do next</trigger>
+            <trigger>At the start of a new project — to see the initialization checklist</trigger>
+        </runs-after>
+        <use-when>
+            <condition>Starting a new project and want to see what needs to be set up</condition>
+            <condition>Returning to a project and want to check initialization status</condition>
+            <condition>Unsure which ACE command to run next</condition>
+        </use-when>
+    </execution-time>
+
+    <input>
+        <flags>
+        </flags>
+
+        <parameters>
+            <required>
+            </required>
+
+            <optional>
+            </optional>
+        </parameters>
+    </input>
+
+    <execution-context>
+        <help-workflow>@~/.claude/agile-context-engineering/workflows/help.xml</help-workflow>
+        <questioning>@~/.claude/agile-context-engineering/utils/questioning.xml</questioning>
+        <ui-formatting>@~/.claude/agile-context-engineering/utils/ui-formatting.md</ui-formatting>
+    </execution-context>
+
+    <output>
+        <objective>
+            Detect which ACE documents exist (product vision, system architecture, system structure,
+            coding standards, testing framework). Display a status dashboard showing what's done
+            and what's missing. Suggest the next command to run based on gaps.
+        </objective>
+
+        <artifacts>
+            - .ace/settings.json (created on first run if missing)
+        </artifacts>
+    </output>
+
+    <process>
+        Execute the help workflow from
+        `@~/.claude/agile-context-engineering/workflows/help.xml` end-to-end.
+        This is a lightweight state-check and routing workflow.
+
+        CRITICAL MANDATORY STEP — DO NOT SKIP:
+        Before displaying the status dashboard, you MUST run:
+        ```bash
+        node ~/.claude/agile-context-engineering/src/ace-tools.js sync-agent-teams --raw
+        ```
+        Then you MUST use `AskUserQuestion` to ask the user whether they want to
+        enable or disable Claude Code Agent Teams (experimental feature).
+        This step is NOT optional. You MUST present this question every time.
+
+        When the user chooses to enable or disable Agent Teams, you MUST run the
+        bash command — NEVER directly edit .ace/settings.json or .claude/settings.json:
+        ```bash
+        node ~/.claude/agile-context-engineering/src/ace-tools.js write-agent-teams true
+        ```
+        or
+        ```bash
+        node ~/.claude/agile-context-engineering/src/ace-tools.js write-agent-teams false
+        ```
+        The write-agent-teams command updates BOTH .ace/settings.json AND .claude/settings.json.
+        Direct file edits will cause the two files to go out of sync.
+    </process>
+
+    <next-steps>
+        **Specialized commands for each document:**
+        - `/ace:plan-product-vision` — Create or update the product vision
+        - `/ace:map-system` — Map codebase structure, architecture, and testing framework
+        - `/ace:init-coding-standards` — Generate tailored coding standards
+    </next-steps>
+
+</command>
+```

package/commands/ace/init-coding-standards.md

@@ -1,83 +1,83 @@
----
-name: ace:init-coding-standards
-description: Generate a tailored coding-standards.md through codebase detection and user interview
-argument-hint: "[optional: context='existing standards doc or notes to build on']"
-allowed-tools:
-  - Read
-  - Bash
-  - Glob
-  - Grep
-  - Write
-  - Task
-  - AskUserQuestion
----
-
-```xml
-<command>
-
-    <execution-time>
-        <runs-after>
-            <trigger>During /ace:help — as part of initial project setup</trigger>
-            <trigger>After /ace:map-system — once codebase is mapped, add prescriptive standards</trigger>
-            <trigger>Anytime — to create or refresh coding standards for a project</trigger>
-        </runs-after>
-        <use-when>
-            <condition>Starting a new project and want to establish coding standards upfront (greenfield or brownfield)</condition>
-            <condition>Onboarding AI agents to an existing codebase (prevents common AI mistakes)</condition>
-            <condition>Current coding standards are outdated or missing</condition>
-            <condition>Team has pain points with AI-generated code quality</condition>
-        </use-when>
-    </execution-time>
-
-    <input>
-        <flags>
-        </flags>
-
-        <parameters>
-            <required>
-            </required>
-
-            <optional>
-                <param name="context" type="file | text">
-                    Existing coding standards document, style guide, or notes
-                    to use as a starting point. Will be refined through the interview process.
-                </param>
-            </optional>
-        </parameters>
-    </input>
-
-    <execution-context>
-        <init-coding-standards-workflow>@~/.claude/agile-context-engineering/workflows/init-coding-standards.xml</init-coding-standards-workflow>
-        <coding-standards-template>@~/.claude/agile-context-engineering/templates/wiki/coding-standards.xml</coding-standards-template>
-        <questioning>@~/.claude/agile-context-engineering/utils/questioning.xml</questioning>
-        <ui-formatting>@~/.claude/agile-context-engineering/utils/ui-formatting.md</ui-formatting>
-    </execution-context>
-
-    <output>
-        <objective>
-            Detect the project's language, paradigm, and frameworks (brownfield) or gather
-            this from the user (greenfield). Interview the user about their coding philosophy
-            and pain points. Generate a tailored, prescriptive coding-standards.md that prevents
-            common AI and developer mistakes.
-        </objective>
-
-        <artifacts>
-            .docs/wiki/system-wide/coding-standards.md
-        </artifacts>
-    </output>
-
-    <process>
-        Execute the init-coding-standards workflow from
-        `@~/.claude/agile-context-engineering/workflows/init-coding-standards.xml` end-to-end.
-        Preserve all workflow gates (validation, approvals, commits).
-    </process>
-
-    <next-steps>
-        **After this command:**
-        - `/ace:map-system` — Map codebase structure and architecture
-        - `/ace:help` — Check project initialization status and next steps
-        - Review and edit `.docs/wiki/system-wide/coding-standards.md` anytime
-    </next-steps>
-
-</command>
-```
+---
+name: ace:init-coding-standards
+description: Generate a tailored coding-standards.md through codebase detection and user interview
+argument-hint: "[optional: context='existing standards doc or notes to build on']"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - Task
+  - AskUserQuestion
+---
+
+```xml
+<command>
+
+    <execution-time>
+        <runs-after>
+            <trigger>During /ace:help — as part of initial project setup</trigger>
+            <trigger>After /ace:map-system — once codebase is mapped, add prescriptive standards</trigger>
+            <trigger>Anytime — to create or refresh coding standards for a project</trigger>
+        </runs-after>
+        <use-when>
+            <condition>Starting a new project and want to establish coding standards upfront (greenfield or brownfield)</condition>
+            <condition>Onboarding AI agents to an existing codebase (prevents common AI mistakes)</condition>
+            <condition>Current coding standards are outdated or missing</condition>
+            <condition>Team has pain points with AI-generated code quality</condition>
+        </use-when>
+    </execution-time>
+
+    <input>
+        <flags>
+        </flags>
+
+        <parameters>
+            <required>
+            </required>
+
+            <optional>
+                <param name="context" type="file | text">
+                    Existing coding standards document, style guide, or notes
+                    to use as a starting point. Will be refined through the interview process.
+                </param>
+            </optional>
+        </parameters>
+    </input>
+
+    <execution-context>
+        <init-coding-standards-workflow>@~/.claude/agile-context-engineering/workflows/init-coding-standards.xml</init-coding-standards-workflow>
+        <coding-standards-template>@~/.claude/agile-context-engineering/templates/wiki/coding-standards.xml</coding-standards-template>
+        <questioning>@~/.claude/agile-context-engineering/utils/questioning.xml</questioning>
+        <ui-formatting>@~/.claude/agile-context-engineering/utils/ui-formatting.md</ui-formatting>
+    </execution-context>
+
+    <output>
+        <objective>
+            Detect the project's language, paradigm, and frameworks (brownfield) or gather
+            this from the user (greenfield). Interview the user about their coding philosophy
+            and pain points. Generate a tailored, prescriptive coding-standards.md that prevents
+            common AI and developer mistakes.
+        </objective>
+
+        <artifacts>
+            .docs/wiki/system-wide/coding-standards.md
+        </artifacts>
+    </output>
+
+    <process>
+        Execute the init-coding-standards workflow from
+        `@~/.claude/agile-context-engineering/workflows/init-coding-standards.xml` end-to-end.
+        Preserve all workflow gates (validation, approvals, commits).
+    </process>
+
+    <next-steps>
+        **After this command:**
+        - `/ace:map-system` — Map codebase structure and architecture
+        - `/ace:help` — Check project initialization status and next steps
+        - Review and edit `.docs/wiki/system-wide/coding-standards.md` anytime
+    </next-steps>
+
+</command>
+```