Ase Sync Reconcile

@${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-arch.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 seven tokens TASK, SPEC, ARCH, CODE, DOCS, INFR, and OTHR. Parse as the comma-separated kind list and 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. Set to the seven recognized kinds TASK,SPEC,ARCH,CODE,DOCS,INFR,OTHR minus all kinds present in . Do not output anything.

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

   5. Remove from any kind that is also present in (a kind is never its own source).

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

   6. Report the resolved target and source with the following :

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

   2. For all kinds in the union of and , 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.

   3. Honor the filtering to reduce the source and/or target artifacts and/or the aspects of those artifacts you should take into account.

   4. Read all (optionally filtered) source and target artifacts previously resolved and build a precise understanding of the current state they represent.

3. 1. Internalize and honor the artifact-format conventions:

      • the artifact-set/artifact/aspect meta information (ase-format-meta.md),
      • the SPEC format (ase-format-spec.md),
      • the ARCH format (ase-format-arch.md),
      • the TASK format (ase-format-task.md).

      Whenever a target artifact belongs to one of these kinds, the update MUST keep it conformant to the corresponding format (headings, structure, identifiers, and the <timestamp-modified/> rule). The kinds CODE, DOCS, INFR, and OTHR have no dedicated format contract and are treated as free-form.

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

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

   4. Bidirectionally update the and artifacts so that they faithfully reflect the current state of each other.

      Unidirectionally update the artifact files so that they faithfully reflect the current state of the artifacts.

      Keep changes as surgical as possible: change only what the input state actually requires, and do not rewrite unrelated parts of an output artifact.

      Apply the update directly to the output artifacts via the Write/Edit tools.

      For each formatted output artifact kind, strictly honor its format contract.

      Whenever an output artifact is changed and contains a Modified: <timestamp-modified-old/> line, replace this with Modified: <timestamp-modified/>.

   5. Report the performed updates with the following , listing one bullet line per changed output file (with its project-relative path and an ultra-brief description of what was reconciled):

      • <file/>: [...]

      Only output the following :