@rse/ase 0.0.55 → 0.0.57

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.55",
+    "version":                              "0.0.57",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.55",
+    "version":     "0.0.57",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.55",
+    "version":     "0.0.57",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/agents/ase-meta-search.md

@@ -4,8 +4,8 @@ description: Query the Web
 model: sonnet
 effort: low
 tools:
-    - "mcp__perplexity__perplexity_search"
-    - "mcp__brave__brave_web_search"
+    - "mcp__search-perplexity__perplexity_search"
+    - "mcp__search-brave__brave_web_search"
     - "mcp__search-exa__web_search_exa"
     - "WebSearch"
 ---

package/plugin/etc/markdownlint.yaml

@@ -15,4 +15,5 @@ no-space-in-code:   false
 ul-indent:          false
 ol-indent:          false
 heading-style:      false
+no-multiple-space-atx: false
 

package/plugin/meta/ase-constitution.md

@@ -3,7 +3,8 @@ ASE Constitution
 ================
 
 You are **Claude Code**, an expert-level AI coding assistant.
-You have the **Agentic Software Engineering (ASE)** facility enabled.
+You have the **Agentic Software Engineering (ASE)** facility enabled,
+which boosts you to an expert-level Software Engineering AI agent.
 
 If <ase-headless/> is empty or not set,
 you *MUST* once and immediately output the following <template/> now:

package/plugin/meta/ase-control.md

@@ -16,12 +16,12 @@ Control Flow Constructs
 -   *IMPORTANT*: You *MUST* honor the following control flow construct:
     <expand name="<define-name/>" [arg1="<expand-arg1/>" [arg2="<expand-arg2/>" [...]]]><expand-content/></expand>:
 
-    This specifies the *expansion* of previous <define/>.
-    This construct is expanded into the <define-body/> of <define/>
-    with `<args/>` substituted with `<expand-arg1/> <expand-arg2/>
-    [...]`, `<arg1/>` substituted with <expand-arg1/>, and `<content/>`
-    substituted with <expand-content/>.
-    Do not output anything else.
+    This specifies the *expansion* of previous <define/>. This
+    construct is expanded to the <define-body/> of <define/> with
+    `<args/>` substituted with `<expand-arg1/> <expand-arg2/> [...]`,
+    `<arg1/>` substituted with <expand-arg1/>, `<arg2/>` substituted
+    with <expand-arg2/>, etc, and `<content/>` substituted with
+    <expand-content/>. Do not output anything else.
 
 -   *IMPORTANT*: You *MUST* honor the following control flow construct:
     <flow><flow-body/></flow>:

package/plugin/meta/ase-dialog.md

@@ -38,7 +38,7 @@ Let the *user interactively choose* an answer.
 
             Start with <n>0</n> (set entry count to zero).
             <for items="2 3 4 5">
-                Take from <config/> the line number <item/>.
+                Take from <spec/> the line number <item/>.
                 If this line does not exist, <break/>.
                 If this line exists, parse it according to the format `<label/>: <description/>`.
                 If <config/> is not empty, set <config><config/>, </config> (append comma).
@@ -93,7 +93,7 @@ Let the *user interactively choose* an answer.
 
             Start with <n>0</n> (set entry count to zero).
             <for items="2 3 4 5">
-                Take from <config/> the line number <item/>.
+                Take from <spec/> the line number <item/>.
                 If this line does not exist, <break/>.
                 If this line exists, parse it according to the format `<label/>: <description/>`.
                 If <config/> is not empty, set <config><config/>, </config> (append comma).

package/plugin/meta/ase-getopt.md

@@ -9,7 +9,7 @@ set placeholders into the context as a side-effect.
 
 1.  **Determine Parameters**:
     Set <getopt-skill><arg1/></getopt-skill>.
-    Set <getopt-spec><arg2/></getopt-spec>.
+    Set <getopt-spec>--help|-h <arg2/></getopt-spec>.
     Set <getopt-opts><arg3/></getopt-opts>.
     Set <getopt-args><content/></getopt-args>.
 
@@ -20,13 +20,14 @@ set placeholders into the context as a side-effect.
     then just silently *SKIP* the following steps 3-7!
 
 3.  **MCP Call**:
-    Call the `ase_getopt(name: <getopt-skill/>, spec: <getopt-spec/>, args:
-    <getopt-args/>)` tool of the `ase` MCP server and set <text/> to the
-    `text` output field of this tool call. The `spec` syntax for each
-    option token is `--<long>[|-<short>][=<default>|=(<c1>|<c2>|...)]`,
-    where `=<default>` declares a value-taking option with a default,
-    and `=(<c1>|<c2>|...)` declares a value-taking option restricted to
-    the listed fixed choices (the first choice acts as the default).
+    Call the `ase_getopt(name: "<getopt-skill/>", spec:
+    "<getopt-spec/>", args: "<getopt-args/>")` tool of the `ase`
+    MCP server and set <text/> to the `text` output field of
+    this tool call. The `spec` syntax for each option token is
+    `--<long>[|-<short>][=<default>|=(<c1>|<c2>|...)]`, where
+    `=<default>` declares a value-taking option with a default, and
+    `=(<c1>|<c2>|...)` declares a value-taking option restricted to the
+    listed fixed choices (the first choice acts as the default).
 
 4.  **Short-Circuit for Error**:
     If <text/> starts with `ERROR:`:
@@ -35,7 +36,7 @@ set placeholders into the context as a side-effect.
     then immediately *STOP* processing the entire current skill:
 
     <template>
-    ⧉ **ASE**: ☻ skill: **<getopt-skill/>**, ▶ ERROR: option parsing failed: **<text/>**
+    ⧉ **ASE**: ✪ skill: **<getopt-skill/>**, ▶ ERROR: option parsing failed: **<text/>**
     </template>
 
 5.  **Parsing JSON Result**:
@@ -47,22 +48,24 @@ set placeholders into the context as a side-effect.
     {
         "opts": { "<long1/>": <value1/>, "<long2/>": <value2/>, ... },
         "argv": [ "<arg1/>", "<arg2/>", ... ],
-        "args": "..."
+        "args": "...",
+        "info": "..."
     }
     ```
 
 6.  **Materializing into Context**:
-    For each *key* `<long/>` in <getopt-result/>`.opts`:
-    Set <getopt-option-<long/>/> to the corresponding value from
-    `<getopt-result/>.opts[<long/>]`.
+    For each *key* `<longN/>` in <getopt-result/>`.opts`:
+    Set <getopt-option-<longN/>/> to the corresponding value
+    `<getopt-result/>.opts[<longN/>]`.
     Set <getopt-arguments/> to the value of `<getopt-result/>.args`.
-    Set <getopt-info/> to `<getopt-result/>.info`.
+    Set <getopt-info/> to `<getopt-result/>.info`, but remove
+    information about the `help` option.
 
 7.  **Display Results**:
     Just output the following <template/>:
 
     <template>
-    ⧉ **ASE**: ☻ skill: **<getopt-skill/>**, ▶ options: <getopt-info/>
+    ⧉ **ASE**: ✪ skill: **<getopt-skill/>**, ▶ options: <getopt-info/>
     </template>
 </define>
 

package/plugin/meta/ase-skill.md

@@ -160,14 +160,23 @@ Skill Identification
 
 - *IMPORTANT*: Set <skill></skill> (set to empty)
   and <skill-name></skill-name> (set name to empty).
-  Then, in case <skill/> later becomes *not* empty
-  by defining it as <skill name="<name/>"><body/></skill>,
-  set <skill-name><name/></skill-name> (set skill name to name),
-  set <skill><body/></skill> (set skill to body), and
-  then you *MUST* once output the following output <template/>:
+
+  In case <skill/> later becomes *not* empty by defining it as <skill
+  name="<name/>"><body/></skill>, set <skill-name><name/></skill-name>
+  (set skill name to name), and then (but only if `$1` is *NOT* equal
+  to `-h` or `--help`) you *MUST* once output the following output
+  <template/>:
+
+  <template>
+  ⧉ **ASE**: ✪ skill: **<skill-name/>**, ✦ purpose: **<skill/>**, ▶ status: **skill started**
+  </template>
+
+  Later (but only if `$1` is *NOT* equal to `-h` or `--help`), once
+  this skill finally will stop processing, you *MUST* once output the
+  following output <template/>:
 
   <template>
-  ⧉ **ASE**: ☻ skill: **<skill-name/>**, ✦ purpose: **<skill/>**, ▶ status: **skill started**
+  ⧉ **ASE**: ✪ skill: **<skill-name/>**, status: **skill finished**
   </template>
 
 - *IMPORTANT*: Set <objective></objective> (set to empty).
@@ -175,6 +184,14 @@ Skill Identification
   you *MUST* once output the following output <template/>:
 
   <template>
-  ⧉ **ASE**: ◎ objective: **<objective/>**
+  ⧉ **ASE**: ✪ skill: **<skill-name/>**, ◎ objective: **<objective/>**
   </template>
 
+- *IMPORTANT*:
+  If `$1` (the first token of the skill arguments) is equal to `-h` or
+  `--help`, you *MUST* once output the following output <template/> and
+  then *IMMEDIATELY* *STOP* the further skill processing:
+
+  <template>
+  @${CLAUDE_SKILL_DIR}/help.md
+  </template>

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.55",
+    "version":                              "0.0.57",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/skills/ase-arch-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-arch-analyze
-argument-hint: "<source-reference>"
+argument-hint: "[--help|-h] <source-reference>"
 description: Review software architecture, including package cohesion and inter-package coupling
 user-invocable: true
 disable-model-invocation: false
@@ -102,20 +102,13 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Review Software Architecture
-============================
-
 <skill name="ase-arch-analyze">
 Review Software Architecture
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software architect*,
-specialized in *reviewing software architecture*.
-</role>
-
 <objective>
-*Review* the *software architecture* of $ARGUMENTS, and its directly
+With the mindset of an *expert-level software architect*,
+*review* the *software architecture* of $ARGUMENTS, and its directly
 related source code, for *potential problems* across component
 boundaries, structural organization, architecture principles,
 interface quality, quality attributes, and architecture governance.

package/plugin/skills/ase-arch-analyze/help.md

@@ -0,0 +1,50 @@
+
+##  NAME
+
+`ase-arch-analyze` - Review Software Architecture
+
+##  SYNOPSIS
+
+`ase-arch-analyze`
+    [`--help`|`-h`]
+    *source-reference*
+
+##  DESCRIPTION
+
+The `ase-arch-analyze` skill reviews the *software architecture* of
+the referenced source code, including *package cohesion* and *inter-
+package coupling*, for *potential problems* across component boundaries,
+structural organization, architecture principles, interface quality,
+quality attributes, and architecture governance.
+
+The skill investigates 21 architecture quality aspects across 7 thematic
+blocks (component boundaries, structural organization, architecture
+principles, interface quality, quality attributes, architecture
+governance, and package cohesion), renders a high-level architecture
+diagram, and reports findings as either `PROBLEM` or `TRADEOFF` entries
+based on a built-in tension matrix.
+
+##  ARGUMENTS
+
+*source-reference*:
+    A file, directory, or other reference to the source code that
+    is to be analyzed architecturally.
+
+##  EXAMPLES
+
+Analyze architecture of the current project:
+
+```text
+❯ /ase-arch-analyze src/
+```
+
+Analyze a specific module:
+
+```text
+❯ /ase-arch-analyze src/core
+```
+
+##  SEE ALSO
+
+`ase-arch-discover`, `ase-code-analyze`, `ase-code-resolve`,
+`ase-code-refactor`, `ase-code-insight`.

package/plugin/skills/ase-arch-discover/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-arch-discover
-argument-hint: "<functionality>"
+argument-hint: "[--help|-h] <functionality>"
 description: >
     Discover additional, third-party components (libraries/frameworks) for
     the technology stack to provide needed functionality.
@@ -17,18 +17,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Discover Components
-===================
-
 <skill name="ase-arch-discover">
 Discover Components
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software architect*,
-specialized in *finding components* (libraries/frameworks) for the technology stack.
-</role>
-
 <objective>
 *Discover* additional, *third-party components* (libraries/frameworks)
 for the technology stack to *provide* the *needed functionality*
@@ -131,12 +123,13 @@ for the technology stack to *provide* the *needed functionality*
             into the already existing result set, but deduplicate
             entries by Maven coordinate.
 
-    -   Call the `ase_component_info(stack: <stack/>, components:
-        [ <package-1/>, ..., <package-N/> ])` tool of the `ase` MCP
+    -   Call the `ase_component_info(stack: "<stack/>", components:
+        [ "<package-1/>", ..., "<package-N/>" ])` tool of the `ase` MCP
         server *once* for the entire set of discovered packages.
         The tool dispatches internally on <stack/> and fetches all
         metadata in maximum parallel and returns an array of objects `{
-        name, version, time, repository, stars, downloads }`. For each
+        name, version, created, updated, repository, stars, downloads,
+        rank }`. For each
         component <component-K/> (K=1-N) read from its corresponding
         entry: <version-K/> from `version`, <updated-K/> from `updated`,
         <created-K/> from `created`, <repository-K/> from `repository`,

package/plugin/skills/ase-arch-discover/help.md

@@ -0,0 +1,48 @@
+
+##  NAME
+
+`ase-arch-discover` - Discover Components
+
+##  SYNOPSIS
+
+`ase-arch-discover`
+    [`--help`|`-h`]
+    *functionality*
+
+##  DESCRIPTION
+
+The `ase-arch-discover` skill discovers additional, *third-party
+components* (libraries/frameworks) for the technology stack that
+provide the needed *functionality*.
+
+The skill determines the project's technology stack (TypeScript,
+JavaScript, Kotlin, or Java), derives essential keywords from the
+requested functionality, queries the corresponding package registry
+(NPM or Maven Central), retrieves metadata (version, downloads,
+stars, dates) via the `ase_component_info` MCP tool, and reports
+the top-ranked components as a Markdown table together with a single
+distinguishing hint (USP, Crux, or Gotcha) per component.
+
+##  ARGUMENTS
+
+*functionality*:
+    A short description of the desired functionality the third-party
+    component should provide.
+
+##  EXAMPLES
+
+Discover components for JSON schema validation:
+
+```text
+❯ /ase-arch-discover JSON schema validation
+```
+
+Discover components for HTTP client functionality:
+
+```text
+❯ /ase-arch-discover HTTP client with retries
+```
+
+##  SEE ALSO
+
+`ase-arch-analyze`, `ase-meta-search`, `ase-meta-evaluate`.

package/plugin/skills/ase-code-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-code-analyze
-argument-hint: "<source-reference>"
+argument-hint: "[--help|-h] <source-reference>"
 description: >
     Analyze the source code for problems in the logic and semantics and its related control flow.
 user-invocable: true
@@ -13,18 +13,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Analyze Source Code
-===================
-
 <skill name="ase-code-analyze">
 Analyze Source Code
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *analyzing source code*.
-</role>
-
 <objective>
 *Analyze* the source code of $ARGUMENTS, and its directly related source
 code, for problems in its *logic* and *semantics* and its related

package/plugin/skills/ase-code-analyze/help.md

@@ -0,0 +1,47 @@
+
+##  NAME
+
+`ase-code-analyze` - Analyze Source Code
+
+##  SYNOPSIS
+
+`ase-code-analyze`
+    [`--help`|`-h`]
+    *source-reference*
+
+##  DESCRIPTION
+
+The `ase-code-analyze` skill analyzes the source code of the referenced
+location, and its directly related source code, for problems in its
+*logic*, *semantics*, and related *control flow*.
+
+The skill investigates the code base silently, reports each detected
+problem as a `PROBLEM` entry with severity (`LOW`, `MEDIUM`, `HIGH`),
+inline file/line references, and persists results in the `ase` MCP
+key/value store as `ase-issue-P<n>` entries so they can later be
+resolved via `ase-code-resolve P<n>`.
+
+##  ARGUMENTS
+
+*source-reference*:
+    A file, directory, function, or other reference to the source code
+    to analyze.
+
+##  EXAMPLES
+
+Analyze a specific source file:
+
+```text
+❯ /ase-code-analyze src/server.ts
+```
+
+Analyze a directory of code:
+
+```text
+❯ /ase-code-analyze src/handlers/
+```
+
+##  SEE ALSO
+
+`ase-code-resolve`, `ase-code-refactor`, `ase-code-lint`,
+`ase-code-explain`, `ase-arch-analyze`.

package/plugin/skills/ase-code-craft/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-code-craft
-argument-hint: "[<task-id>:] <feature>"
+argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <feature>"
 description: >
     Craft Source Code:
     Use when user wants to create or craft a new feature from scratch.
@@ -17,9 +17,6 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Craft Feature
-=============
-
 <skill name="ase-code-craft">
 Craft Source Code
 </skill>
@@ -30,10 +27,6 @@ Craft Source Code
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*.
-</role>
-
 <objective>
 From scratch *craft* the following feature:
 <feature><getopt-arguments/></feature>
@@ -61,7 +54,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id><feature/></ase-task-id> (set task id to feature)
         and <feature></feature> (set feature empty), call the
-        `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
+        `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool
         from the `ase` MCP server to switch the task, and then only
         output the following <template/>:
 
@@ -73,8 +66,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  If <feature/> has the format `<id/>: <text/>` where <id/> matches
         the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
         <feature><text/></feature> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: <ase-task-id/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP server to
+        and call the `ase_task_id(id: "<ase-task-id/>", session:
+        "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
 
     3.  If <feature/> is empty,
@@ -91,8 +84,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id/> to a unique task id, derived from <feature/>,
         which consists of two lower-case words concatenated with a
-        `-` character. Then call the `ase_task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP server to
+        `-` character. Then call the `ase_task_id(id: "<ase-task-id/>",
+        session: "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
         </if>
 
@@ -279,7 +272,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         words <words/> of <content/>.
 
     3.  You *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: <ase-task-id/>, text: <content/>)`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
 
     4.  Output a hint with the following <template/>:
 
@@ -287,9 +280,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    5.  Directly pass-through control to the `ase:ase-task-edit` skill.
-        Set <args></args> (set args to empty). If <getopt-option-next/>
-        is not equal `none`, set <args><args/> --next
-        <getopt-option-next/></args> (append to args). Then call the
-        tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+    5.  Directly pass-through control to the next skill:
+
+        1.  <if condition="<getopt-option-next/> is equal `IMPLEMENT`">
+            Call the tool `Skill(skill: "ase:ase-task-implement")` to
+            *implement* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        2.  <if condition="<getopt-option-next/> is equal `PREFLIGHT`">
+            Call the tool `Skill(skill: "ase:ase-task-preflight")` to
+            *preflight* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        3.  <if condition="
+                <getopt-option-next/> is not equal `IMPLEMENT` AND
+                <getopt-option-next/> is not equal `PREFLIGHT`
+            ">
+            Set <args></args> (set args to empty).
+            <if condition="<getopt-option-next/> is not equal `none`">
+            Set <args><args/> --next <getopt-option-next/></args> (append to args).
+            </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            </if>
 

package/plugin/skills/ase-code-craft/help.md

@@ -0,0 +1,66 @@
+
+##  NAME
+
+`ase-code-craft` - Craft Source Code
+
+##  SYNOPSIS
+
+`ase-code-craft`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--next`|`-n` *option*]
+    [*task-id*:] *feature*
+
+##  DESCRIPTION
+
+The `ase-code-craft` skill crafts a *new feature* from scratch by
+investigating the existing code base, internalizing crafting tenets
+(KISS, YAGNI, DRY, SRP, loose coupling, ...), proposing one or more
+*feature approaches* with pros and cons, letting the user pick the
+preferred approach, and composing a corresponding *task plan* aligned
+with the existing architecture.
+
+The skill does *not* directly modify source files. It persists the
+plan via `ase_task_save` and then hands off to `ase-task-edit`,
+`ase-task-preflight`, or `ase-task-implement`, as selected by
+`--next`.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically pick the recommended feature approach without
+    asking the user via the interactive dialog.
+
+`--next`|`-n` *option*:
+    Automatically choose the next step after composing the plan,
+    where *option* is either `none` (default, hand-off to
+    `ase-task-edit` interactively), `DONE` (stop), `EDIT` (hand off
+    to `ase-task-edit`), `PREFLIGHT` (hand off to
+    `ase-task-preflight`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+[*task-id*:] *feature*:
+    Description of the *feature* to craft. Optionally prefixed with
+    a *task-id* followed by a colon to bind the resulting plan to
+    a specific task id.
+
+##  EXAMPLES
+
+Craft a new logging feature:
+
+```text
+❯ /ase-code-craft add structured JSON logging with log levels
+```
+
+Craft a feature under a named task and directly hand off to implementation:
+
+```text
+❯ /ase-code-craft --next IMPLEMENT auth: add JWT authentication middleware
+```
+
+##  SEE ALSO
+
+`ase-code-refactor`, `ase-code-resolve`, `ase-task-edit`,
+`ase-task-preflight`, `ase-task-implement`.