ase-sync-import

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

$ARGUMENTS

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

Procedure

1. 1. The recognized artifact kinds are the six tokens TASK, SPEC, CODE, DOCS, INFR, and OTHR. Parse as the comma-separated kind list. Upper-case and trim every parsed kind token. Do not output anything.

   2. Only output the following and then immediately STOP processing the entire current skill:

   3. If any token in is not one of the six recognized kinds, only output the following (with set to the first offending token) and then immediately STOP processing the entire current skill:

   4. Only output the following and then immediately STOP processing the entire current skill:

   5. Report the resolved target and source hint with the following :

2. 1. Do not output anything in this STEP 2.

   2. Interpret the as the description of the foreign sources to import from. The foreign sources are external to the ASE artifact sets and may be local files or directories, remote URLs, pasted text passages, or references to other documents.

   3. Read or fetch all foreign sources named by the : read local files and directories via the Read tool, and fetch remote URLs via the available web tools. Build a precise understanding of the information the foreign sources represent.

3. 1. For all kinds in except TASK, call the ase_artifact_list(kind: [ ... ]) tool of the ase MCP server once, passing the lower-cased kind tokens, and read the returned artifacts array of { kind, files } objects to obtain the project-relative file list per kind. The TASK kind is not resolvable via ase_artifact_list (task plans are managed by the ase_task_* tools), so resolve and read it via the ase_task_id and ase_task_load tools instead. Read all existing target artifacts to understand their current state.

   2. Internalize and honor the artifact-format conventions:

      • the artifact-set meta information (ase-format-meta.md),
      • the SPEC format, i.e. the SpecBook models and formats plus the SpecBook schema configuration of the project (ase-format-spec.md),
      • the TASK format (ase-format-task.md).

      Whenever a target artifact belongs to one of these kinds, it MUST be kept (or made) conformant to the corresponding format (headings, structure, identifiers, references, and the Modified: timestamp rule). The kinds CODE, DOCS, INFR, and OTHR have no dedicated format contract and are treated as free-form.

   3. You MUST internalize and strictly honor the GENERIC TENETS, the CRAFTING TENETS, and the RECONCILIATION TENETS of the ASE Tenets when generating or updating in the following. Do not output anything.

   4. Call the ase_timestamp(format: "yyyy-LL-dd HH:mm") tool of the ase MCP server once to find out the current time and store it in .

   5. Generate or update the artifact files so that they faithfully reflect the information of the imported foreign sources:

      • Generate a target artifact that does not yet exist but is warranted by the imported information, using the current time for both its Created: and Modified: timestamps.

      • Update an existing target artifact so it reflects the imported information. Keep changes as surgical as possible: change only what the imported information actually requires, and do not rewrite unrelated parts of an artifact. Whenever an existing artifact is changed and contains a Modified: <timestamp-modified-old/> line, replace this with Modified: <timestamp-modified/>.

      Honor No Fabrication: never invent target content the foreign sources do not support; if the sources are silent or ambiguous on something the target needs, surface the gap rather than guessing. Re-express the imported facts at the target's level of abstraction (a SPEC states intent and structure).

      Apply the generation/update directly to the target artifacts via the Write/Edit tools. For a TASK target, apply it via the ase_task_save MCP tool instead -- NEVER write a task plan file via Write/Edit or by executing a shell command.

   6. Validate the specification by calling the ase_specbook_lint() tool of the ase MCP server and reading its returned diagnostics array of { file, line, column, severity, message } objects. If it is not empty, fix the reported problems in the affected SPEC artifacts via the Write/Edit tools and call the tool again -- for at most three rounds in total. Do not output anything, unless diagnostics remain after the last round, in which case output the following , listing one bullet line per remaining diagnostic:

      • <file/>:<line/>:<column/>: [...]

   7. Report the performed changes with the following , listing one bullet line per generated or updated file (with its project-relative path and an ultra-brief description of what was imported):

      • <file/>: [...]

      Only output the following :

   8. Finally, give the closing hint by expanding the following (which, depending on the configured , may expand into nothing and hence emit no output at all):