npm - agile-context-engineering - Versions diffs - 0.3.0 → 0.5.1 - Mend

agile-context-engineering 0.3.0 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (139) hide show

package/agile-context-engineering/templates/_command.md DELETED Viewed

@@ -1,54 +0,0 @@
----
-name: ace:COMMAND_NAME
-description: COMMAND_DESCRIPTION
-argument-hint: ""
-allowed-tools:
-  - Read
-  - Bash
-  - Glob
-  - Grep
-  - Write
-  - Task
----
-```xml
-<command>
-	<execution-time>
-	</execution-time>
-    <input>
-        <flags>
-		</flags>
-        <parameters>
-            <required>
-			</required>
-            <optional>
-			</optional>
-        </parameters>
-    </input>
-    <execution-context>
-    </execution-context>
-    <output>
-        <objective>
-        </objective>
-        <artifacts>
-        </artifacts>
-    </output>
-    <process>
-    </process>
-    <success_criteria>
-    </success_criteria>
-    <next-steps>
-    </next-steps>
-</command>
-```

package/agile-context-engineering/templates/_workflow.xml DELETED Viewed

@@ -1,17 +0,0 @@
-<workflow>
-    <purpose>
-    </purpose>
-    <mandatory-context>
-        [TODO] Read all files referenced by the invoking prompt's execution-context before starting. Also Read any document or text passed as parameter in the invoking command that called this template.
-    </mandatory-context>
-    <process>
-        <step name="1">
-        </step>
-        <step name="2">
-        </step>
-    </process>
-</workflow>

package/agile-context-engineering/templates/config.json DELETED Viewed

File without changes

package/agile-context-engineering/templates/product/integration-solution.xml DELETED Viewed

File without changes

package/commands/ace/help.md DELETED Viewed

@@ -1,93 +0,0 @@
----
-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>
-```