Kiro packaging

July 7, 2026 · View on GitHub

Kiro packaging for the agentic traceability tool. Reuses ../common/ verbatim (deterministic tools, methodology, config); only the orchestration wrapper differs.

Status: implemented

Install with ./install.sh --ide kiro, then in Kiro ask "generate a traceability matrix".

How it works

Kiro drives agents through steering docs under .kiro/steering/. The tool is packaged as:

  • steering/traceability.md — a steering doc that orchestrates the pipeline: run discovery, compute the active chain, bridge adjacent layers, validate + merge, build the reports. It reads bridge methodology from .kiro/traceability/methodology/*.md (installed from ../common/methodology/).
  • Tools are invoked by shelling out to .kiro/traceability/tools/discover_artifacts.py and build_matrix.py (stdlib Python, no deps).

Key difference from Claude: Kiro has no parallel subagent fan-out, so the relationship bridges run sequentially in the single agent loop — the agent reads each methodology file and applies it itself, in chain order, rather than dispatching the trace-* subagents. The deterministic tools and the methodology content are identical to the Claude packaging.

Source vs. install target

This kiro/ folder is source (tracked). The installer writes the target .kiro/traceability/ and .kiro/steering/traceability.md, which are gitignored and regenerated. Any pre-existing unrelated .kiro/ content (e.g. an AIDLC workflow) is left untouched.

install.sh --ide kiro produces:

  • ../common/tools/* → .kiro/traceability/tools/
  • ../common/methodology/* → .kiro/traceability/methodology/
  • common/trace-config.yaml → .kiro/traceability/trace-config.yaml
  • kiro/steering/traceability.md → .kiro/steering/traceability.md
  • kiro/agents/traceability.json → .kiro/agents/traceability.json

Usage

./install.sh --ide kiro
kiro-cli chat --agent traceability

Then say "generate a traceability matrix" (optionally with a project path). The agent config auto-approves the Python tool invocations and read-only commands so the run proceeds without prompts. Writes are restricted to ./aidlc-docs/traceability/** and /tmp/**.