kiro-to-grill

Detects unregistered domain terms and ADR candidates in Kiro specs and syncs them to CONTEXT.md.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-to-grill-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-to-grill
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-to-grill
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-to-grill-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kiro specs accumulate domain terminology, invariants, and design decisions that never make it back into the authoritative domain docs, causing glossary drift and undocumented architectural choices. This Skill reconciles Kiro specs with CONTEXT.md and docs/adr/* so the domain model stays the single source of truth. ## Core Features & Use Cases - Terminology Extraction: Scans .kiro/specs/** for unregistered ubiquitous language, canonical terms, avoid terms, invariants, boundary names, and contract names, then classifies each as registered, missing, conflict, needs_grill, or ignore. - ADR Candidate Detection: Identifies irreversible, non-obvious, trade-off-laden design decisions in requirements/design/tasks changes and proposes them as ADRs. - Reconciliation Report: Produces a Kiro to Grill Report before editing, resolves ambiguities through domain-modeling / grill-with-docs, then updates CONTEXT.md and docs/adr/* without touching the specs. - Use Case: After a feature spec changes, ask the assistant to review .kiro/specs for undefined terms; it lists glossary gaps and ADR candidates, confirms meanings with you, and updates CONTEXT.md and the ADR directory accordingly. ## Quick Start Review the specs under .kiro/specs, find any unregistered ubiquitous language, and update CONTEXT.md and docs/adr with the confirmed terms and decisions.

Frequently Asked Questions about kiro-to-grill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Kiro spec terminology back into a domain glossary?

Run this Skill against .kiro/specs to extract candidate domain terms, invariants, and boundary names. It classifies each against CONTEXT.md as registered, missing, or conflicting, then updates the glossary after confirming meanings with you.

How do I find ADR candidates in Kiro spec changes?

The Skill scans requirements, design, and tasks changes for irreversible, non-obvious decisions with trade-offs, such as data ownership or contract changes. It lists them in a report and creates ADRs in docs/adr/ only when all three criteria are met.

Does this Skill modify the Kiro spec files themselves?

No. The .kiro/specs/** files are read-only sources for this Skill. It only writes to CONTEXT.md and docs/adr/*, and it never edits specs unless the user explicitly instructs it outside this workflow.

What happens when a spec term conflicts with CONTEXT.md?

Conflicts are flagged in the Kiro to Grill Report instead of being silently overwritten. The Skill asks which side is authoritative, resolves the meaning through domain-modeling or grill-with-docs questioning, and only then applies the update.

When should I not use this reconciliation workflow?

Do not use it for generating requirements, design, or tasks, checking spec status, or refining raw requirements before handing them to Kiro. For pre-spec requirement refinement, use the grill-to-kiro direction instead.