agile-context-engineering 0.5.0 → 0.5.1

package/skills/plan-feature/SKILL.md

@@ -1,76 +1,99 @@
----
-name: plan-feature
-description: Plan a feature through backlog-aware questioning, story decomposition, and guided feature specification
-argument-hint: "[feature-id] [optional: context='text or file with feature description prompt']"
-disable-model-invocation: true
-allowed-tools: Read, Bash, Write, Task, AskUserQuestion
-model: opus
-effort: high
----
-
-# Plan Feature
-
-Plan a feature through backlog-aware questioning, story decomposition, and guided feature specification.
-
-## When to Use
-
-- After `/ace:plan-backlog` — once the backlog exists, plan individual features
-- Anytime — to create or refine a feature and its story breakdown
-- Product backlog exists and you want to break a feature into stories
-- Starting feature-level planning and need to decompose into stories
-- Refining an existing feature with updated acceptance criteria or scope
-- Adding a new feature to an existing epic
-
-## Input
-
-### Optional
-
-- **`feature-id`** — Feature identifier from the product backlog (e.g., F3, #78). If provided, locates existing feature for planning or refinement. If omitted, presents the backlog for selection or allows creating a new feature.
-- **`context`** — Feature description, acceptance criteria, user stories, or any context to seed the feature planning process. Will be absorbed and refined through questioning, not used as-is.
-
-## 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
-- **Feature template**: Read [feature-template.xml](feature-template.xml) — output format for the feature specification
-- **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 requirements gathering, deep questioning, and feature specification.
-
-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
-
-```
-.ace/artifacts/product/<id-epic_name>/<id-feature_name>/<id-feature_name>.md
-.ace/artifacts/product/<id-epic_name>/<id-feature_name>/<id-story_name>/<id-story_name>.md
-```
-
-## Example Usage
-
-```
-# Plan a feature by ID from the backlog
-/ace:plan-feature F3
-
-# Plan a feature with seed context
-/ace:plan-feature context="OAuth2 login with Google and GitHub providers"
-
-# Plan a feature by GitHub issue number
-/ace:plan-feature #78
-```
-
-## Next Steps
-
-- `/ace:plan-story story=...` — Plan a story from this feature
-- `/ace:plan-feature feature-id` — Plan another feature
-- `/ace:help` — Check project initialization status
+---
+name: plan-feature
+description: Plan a feature through backlog-aware questioning, story decomposition, and guided feature specification
+argument-hint: "[feature-id] [optional: context='text or file with feature description prompt']"
+disable-model-invocation: true
+allowed-tools: Read, Bash, Write, Task, AskUserQuestion
+model: opus
+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}/feature-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>After /ace:plan-backlog — once the backlog exists, plan individual features</trigger>
+            <trigger>Anytime — to create or refine a feature and its story breakdown</trigger>
+        </runs-after>
+        <use-when>
+            <condition>Product backlog exists and you want to break a feature into stories</condition>
+            <condition>Starting feature-level planning and need to decompose into stories</condition>
+            <condition>Refining an existing feature with updated acceptance criteria or scope</condition>
+            <condition>Adding a new feature to an existing epic</condition>
+        </use-when>
+    </execution-time>
+
+    <input>
+        <flags>
+        </flags>
+
+        <parameters>
+            <required>
+            </required>
+
+            <optional>
+                <param name="feature-id" type="text">
+                    Feature identifier from the product backlog (e.g., F3, #78).
+                    If provided, locates existing feature for planning or refinement.
+                    If omitted, presents the backlog for selection or allows creating
+                    a new feature.
+                </param>
+                <param name="context" type="file | text">
+                    Feature description, acceptance criteria, user stories, or any
+                    context to seed the feature planning process. Will be absorbed and
+                    refined through questioning, not used as-is.
+                </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 environment, load the product backlog and epic context,
+            absorb any user-provided feature description, conduct deep questioning to
+            define feature scope and acceptance criteria, decompose the feature into
+            stories, and generate feature and story artifact files.
+            Optionally create GitHub issues if github-project.enabled=true.
+        </objective>
+
+        <artifacts>
+            .ace/artifacts/product/<id-epic_name>/<id-feature_name>/<id-feature_name>.md
+            .ace/artifacts/product/<id-epic_name>/<id-feature_name>/<id-story_name>/<id-story_name>.md
+        </artifacts>
+    </output>
+
+    <process>
+        Execute the plan-feature workflow from
+        `workflow.xml` end-to-end.
+        Preserve all workflow gates (validation, approvals, commits).
+    </process>
+
+    <next-steps>
+        **After this command:**
+        - `/ace:plan-story story-id` — Plan a story
+        - `/ace:plan-feature feature-id` — Plan another feature
+        - `/ace:help` — Check project initialization status
+    </next-steps>
+
+</command>
+```