ase-code-craft

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

$ARGUMENTS

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md

Procedure

1. 1. Set (set task id to feature) and (set feature empty), call the 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 :

   2. Set and 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. **No feature known yet. What is the feature you want to craft?**

      Then set to the response of the user.

   4. Set to a unique task id, derived from , 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 implicitly switch the task. Do not output anything.

   5. Report the task and feature with the following :

   6. Figure out what the requested to be crafted is about.

   7. Ask the user for clarification if the goal of this crafting is too unclear.

   8. Do not output anything else in this step, unless you asked the user.

2. 1. Check the existing source files for all code which is related to the requested new .

   2. Check the architecture of the existing code base to understand the overall structures and dynamics.

   3. Do not output anything in this STEP 2.

3. 1. CRAFTING

   3. Do not output anything in this STEP 3.

4. 1. Directly craft the by modifying the affected artifacts with a corresponding, complete change set, based on your gathered knowledge about the code base and your internalized crafting tenets. Also, if a CHANGELOG.md file exists, make an appropriate entry there, too.

   2. Output only the following :

   3. 1. In the following, you MUST NOT use your built-in tool! Instead, you MUST just show a custom dialog according to the expanded custom-dialog definition. You MUST closely follow this definition.

         Ask the user for the next change with the following custom dialog:

      2. If is DONE or CANCEL, .

      3. Otherwise has the format OTHER: <text/>: set to , then directly craft it and report it exactly as specified by the items 1 and 2 above (including the CHANGELOG.md entry).

   4. Then IMMEDIATELY STOP all further skill processing. You MUST NOT output anything else in this STEP 4 or after it -- independent of , whose exposure rules are explicitly overridden here. Especially, do not output a change summary, a list of modified artifacts, a rationale, or a unified diff of the changes.

   1. Compose a feature plan for the chosen feature A by closely aligning to the existing architecture and the existing code base. Use the defined for a task plan and inject the information from feature A and all derived realization decisions into it. Store the resulting task plan in .

      If a CHANGELOG.md file exists in the project (or in any affected sub-package), the plan MUST include, as part of its ## CHANGES section, an explicit bullet point describing the addition of a corresponding new entry to that CHANGELOG.md file, aligned with its existing style and conventions.

      You MUST NOT call Edit, Write, NotebookEdit, or any filesystem-modifying tool during this step.

   2. Call the ase_timestamp(format: "yyyy-LL-dd HH:mm") tool of the ase MCP server and use the text field of its response for and information. Then insert the current , , , and information.

   3. You then MUST save the resulting plan content with the ase_task_save(id: "<ase-task-id/>", text: "<task-content/>") MCP tool call only -- NEVER by executing a shell command.

   4. Output a hint with the following :

   5. Directly pass-through control to the next skill: