agile-context-engineering 0.5.0 → 0.5.1

package/skills/help/workflow.xml

@@ -8,7 +8,7 @@
     </purpose>
 
     <mandatory-context>
-        Read all files referenced by the invoking prompt's execution-context before starting.
+        All supporting resource files are auto-loaded in the skill prompt above. Do NOT re-read them.
     </mandatory-context>
 
     <process>
@@ -238,8 +238,19 @@
         <step name="agent-teams-setup" order="4">
             **MANDATORY — MUST execute this step. DO NOT skip. Always ask the user about Agent Teams.**
 
-            This step syncs and configures the Claude Code Agent Teams experimental feature.
-            You MUST run the sync command below and MUST use AskUserQuestion to interact with the user.
+            This step syncs and configures the Claude Code Agent Teams experimental feature.
+            You MUST run the sync command below and MUST use AskUserQuestion to interact with the user.
+
+            <conditional condition="INIT.runtime_config_dir is '.codex'">
+                Codex does not support Claude Code Agent Teams. Run sync-agent-teams so
+                `.ace/settings.json` records `agent_teams: false`, then skip the user prompt.
+
+                ```bash
+                node "${CLAUDE_SKILL_DIR}/script.js" sync-agent-teams --raw
+                ```
+
+                Continue to step 5.
+            </conditional>
 
             <substep order="4.1" name="sync-agent-teams">
                 **MANDATORY — Run this command before evaluating state:**

package/skills/init-coding-standards/SKILL.md

@@ -1,72 +1,91 @@
----
-name: 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']"
-disable-model-invocation: true
-allowed-tools: Read, Bash, Glob, Grep, Write, Task, AskUserQuestion
-model: sonnet
-effort: high
----
-
-# Init Coding Standards
-
-Generate a tailored coding-standards.md through codebase detection and user interview.
-
-## When to Use
-
-- During `/ace:help` — as part of initial project setup
-- After `/ace:map-system` — once codebase is mapped, add prescriptive standards
-- Anytime — to create or refresh coding standards for a project
-- Starting a new project and want to establish coding standards upfront (greenfield or brownfield)
-- Onboarding AI agents to an existing codebase (prevents common AI mistakes)
-- Current coding standards are outdated or missing
-- Team has pain points with AI-generated code quality
-
-## Input
-
-### Optional
-
-- **`context`** — Existing coding standards document, style guide, or notes to use as a starting point. Will be refined through the interview process.
-
-## Environment Context (preprocessed)
-
-!`node "${CLAUDE_SKILL_DIR}/script.js" init "$ARGUMENTS" 2>/dev/null`
-
-## Supporting Resources
-
-Read ALL of these before starting the workflow:
-
-- **Workflow**: Read [workflow.xml](workflow.xml) — complete orchestration process with all steps
-- **Coding standards template**: Read [coding-standards-template.xml](coding-standards-template.xml) — output format for the coding standards
-- **Questioning guide**: Read `${CLAUDE_SKILL_DIR}/../../shared/utils/questioning.xml` — deep questioning techniques
-- **UI formatting**: Read `${CLAUDE_SKILL_DIR}/../../shared/utils/ui-formatting.md` — ACE output formatting rules
-
-## Process
-
-Use the `ace-product-owner` agent for interviewing the user about coding philosophy and pain points.
-
-The Environment Context above contains the preprocessed INIT JSON — use it directly instead of running the init script manually. The workflow's step 1 setup can skip the init bash call since that data is already available.
-
-Read all supporting resources listed above, then execute the workflow defined in [workflow.xml](workflow.xml) end-to-end. Preserve all workflow gates (validation, approvals, commits).
-
-## Artifacts
-
-```
-.docs/wiki/system-wide/coding-standards.md
-```
-
-## Example Usage
-
-```
-# Generate coding standards from codebase analysis + interview
-/ace:init-coding-standards
-
-# Generate with existing standards as seed
-/ace:init-coding-standards context="path/to/existing-style-guide.md"
-```
-
-## Next Steps
-
-- `/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
+---
+name: 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']"
+disable-model-invocation: true
+allowed-tools: Read, Bash, Glob, Grep, Write, Task, AskUserQuestion
+model: sonnet
+effort: high
+---
+
+## Environment Context (preprocessed)
+
+!`node "${CLAUDE_SKILL_DIR}/script.js" init 2>/dev/null`
+
+## Supporting Resources (auto-loaded)
+
+!`cat "${CLAUDE_SKILL_DIR}/workflow.xml"`
+
+!`cat "${CLAUDE_SKILL_DIR}/coding-standards-template.xml"`
+
+!`cat "${CLAUDE_SKILL_DIR}/../../shared/utils/questioning.xml"`
+
+!`cat "${CLAUDE_SKILL_DIR}/../../shared/utils/ui-formatting.md"`
+
+```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>
+        <!-- All supporting files are auto-loaded in the Supporting Resources section above.
+             The model does NOT need to Read these files — they are already in context. -->
+    </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
+        `workflow.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>
+```