Kiro

Vendor: AWS Install name: kiro Status: GA Native config: <project>/.kiro/steering/apothem-rules.md

Installation

apothem install --harness kiro --project /path/to/project

The adapter writes one project-scope Kiro steering file from the shared Apothem rules and governance surface.

Files written: <project>/.kiro/steering/apothem-rules.md

Profile-to-native-config mapping

The adapter reads Apothem's shared profile and renders the project steering file on every apothem install or apothem update run. The shared profile is the source of truth; project-local edits to the generated file are backed up before the next sync replaces the Apothem-managed content.

Compatibility notes

Kiro's steering surface is project-scoped under .kiro/steering/. The adapter writes a dedicated apothem-rules.md steering file with inclusion: always front matter and never clobbers Kiro's operator-authored foundation files (product.md, tech.md, structure.md). Kiro specs (.kiro/specs/) and agent hooks are operator-owned; Apothem does not write them.

Verification

apothem verify --harness kiro --project /path/to/project

The verify command confirms that:

1. The native config exists at the expected path.
2. All mandatory fields from the shared profile are present.
3. The adapter-specific verification routine reports success.

Updating

apothem update --harness kiro --project /path/to/project

Re-derives the project steering file from the current shared profile state.

Uninstalling

apothem uninstall --harness kiro --project /path/to/project

Removes the native config files written by the adapter. The shared profile YAML and Apothem engine are unaffected.

Conformity gate

python -m apothem.conformity.gate --all .

Troubleshooting

Configuration knobs

See also

• All harnesses — the full catalog of supported tools
• Install guide — install Apothem into this harness
• apothem harnesses reference — list and inspect adapters from the CLI