agentsclimarketplace

Context sync

Skill LaProgrammerie/ai-engineering-core/skills/context-sync

Global Kiro steering + skills — portable AI engineering layer. Pairs with template-generic-project (spec → handoff → code).

Install
npx -y skills add LaProgrammerie/ai-engineering-core --skill context-sync

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Compare Kiro spec artefacts with current-spec.md and handoff.md; flag drift and list required doc updates before or after implementation.

SKILL.md

1.9 KB, as published. Nobody here has run it

Context sync (global)

Objective

Check alignment between native spec, cross-tool summary, and execution contract; surface drift and suggest concrete updates — without editing the repo unless the user asks.

When to use

  • After material changes under .kiro/specs/<feature>/
  • Before a big implementation push
  • When behaviour or code no longer matches written scope
  • Periodic hygiene on active work

Expected inputs

  • Feature folder path under .kiro/specs/ (if present)
  • Paths to docs/ai/active/current-spec.md and docs/ai/active/handoff.md if the repo uses that layout (or equivalents)
  • Optional: recent code change summary

Steps

  1. Read tasks (and design/requirements if needed) under .kiro/specs/<feature>/.

  2. Read current-spec.md: State, summary, scope, acceptance criteria.

  3. Read handoff.md: allowed scope, files to change / not change, plan, DoD.

  4. Compare triple:

    • Does current-spec.md reflect the same scope and phase as the spec folder?
    • Does handoff.md match the current tasks and design intent?
    • Any implicit work in handoff that is not in tasks (or the reverse)?

  5. For each mismatch, propose exactly what to edit (file + section + intent), in order: spec → current-spec.md → handoff.md → code.

Output format

  • Aligned / Drift detected (one-line verdict)
  • Drift table: item | location A | location B | suggested fix
  • Ordered action list (what to update first)
  • If no project uses this layout, state that and stop — do not invent paths

Rules

  • Stay global / portable: no repo-specific stack rules; only the sync pattern between spec artefacts and projections.
  • Do not assume hooks auto-fixed anything.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.