tadeumendonca-skills — Kiro Power

This directory is the Kiro Power package root for tedeuxx/tadeumendonca-skills. It is generated from the repository's own skills/ tree and gated by hooks/scripts/kiro-power.test.sh; editing it by hand will turn that gate red. Edit skills/<name>/SKILL.md at the repository root instead.

What changed since an earlier release of this file. Earlier releases said the question of whether a Kiro build implementing the Agent Plugins format would carry agents/ and hooks/ was unmeasured and claimed in neither direction. It is measured now — against Kiro 1.0.337, on 2026-08-23 — and the answer splits in two: transport yes, activation no (see What this ships below). The struck text and the full round-by-round history are kept at the source, in the repository's own README.md. This file is regenerated and republished on every merge, so it carries current claims only.

Install

In Kiro: Powers panel -> Add Custom Power -> Import power from GitHub, then enter

https://github.com/tedeuxx/tadeumendonca-skills/tree/main/powers/tadeumendonca-skills

The /tree/main/<path> form is required, not optional. Kiro parses the branch and the sub-path out of the URL and sparse-checks-out that directory; a bare repository URL resolves the package root to the repository root, where there is no Kiro manifest.

Read "One caveat" below before you rely on this. Old enough builds report a successful install and copy nothing, so the steps above can appear to work and leave you with an empty Power.

What this ships, and what it does not

Ships: the skills — 15 dense, project-agnostic engineering guides.

Does not ship: the harness's persona briefs (agents/), its PreToolUse permission hooks (hooks/), its typed commands (commands/) or its merge gates. This export carries the knowledge layer and not the enforcement layer BY CHOICE, which is a fact about this package and needs no reading of anybody else's installer: the enforcement layer is Claude-Code-shaped — hooks.json, PreToolUse matchers, agent_type — and porting it to another harness is work nobody has done, not a file anybody forgot to copy.

Whether a Kiro build implementing the Agent Plugins format WOULD carry those directories has two halves, with opposite answers. Read out of the installed Kiro 1.0.337 (quality: stable, bundle built 2026-08-18):

• Transport — yes. The installer branches on whether the package holds a plugin.json. If it does, it copies the whole tree with a single exclusion (.git). agents/ and hooks/ would arrive on disk.
• Activation — no. The loader's filename constants are exactly plugin.json, mcp.json, skills/SKILL.md and dev.kiro. Nothing walks agents/, hooks/ or commands/, and ~/.kiro/powers/ is never scanned for a persona or a hook.

commands/ was absent from that list until 2026-09-10, and its absence was this section's own named failure shape arriving through the door this section exists to close — silence reading as present. The skills below cite a typed command 37 times by identifier and a commands/*.md path 10 times more; every one of those citations is correct for a Claude Code reader and resolves to nothing inside this package. Re-derive both from the package root rather than trusting the digits, with grep -rhoE '/(autonomy|blueprint|funnel-review|new-issue|sprint-planning|sprint-retrospective|sprint-review)' skills | wc -l and grep -rhoE 'commands/[a-z-]+\.md' skills | wc -l, calibrated against grep -rhoF /devops skills | wc -l — a name that DOES resolve here, so a zero from the first two would be a real zero and not a dead pattern. The first selector is an ENUMERATION of the seven commands that existed when this file was generated, and it cannot be anything else from inside this package — the directory it would derive them from is the directory this package does not ship. The seventh arrived at #401, and the sentence that stood here predicted exactly what would have happened if nobody had touched this line: it would have been cited here and counted by nothing, and the figure would have gone quietly low rather than wrong. It is 34 under the old selector and 37 under this one, over the same tree — that gap is the whole of the failure mode, made visible once. An eighth command has the same exposure and nothing will announce it. The source-side check is ls commands/*.md in the repository, against the seven names in the selector. The citations are deliberately not swept out of the skill bodies: they are right for the majority reader, and thinning fifteen skills for a minority target would spend content to buy a silence. And nothing gates any of this — the regeneration diff compares this file against the generator that wrote it, so both sides move together by construction, and no check anywhere counts a citation or asks whether a cited directory ships.

Keep those two words apart, because the gap between them is why omitting the enforcement layer is a reason and not only a preference. A directory that is copied but never read sits next to skills that do load, and reads as installed. A missing directory announces itself; an inert one does not.

This is a bundle reading, not a live install. Nothing above was observed loading, activating or denying anything: no Power has ever been installed from this repository. What would settle it is ten minutes of an authenticated Kiro session — Powers → Add Custom Power → Import power from local folder, with sentinel files planted in agents/ and hooks/ — then reading ~/.kiro/powers/installed/ for what arrived and the agent's behaviour for what activated.

So, whichever half you care about: install this expecting the skills, not the denies. The full harness is the Claude Code plugin at the repository root.

One caveat, and it is larger than the rest

Measured, not inferred — and measured by reading the shipped Kiro bundle, not by running a live install. Every claim here comes from the installed Kiro 1.0.337 (quality: stable, bundle built 2026-08-18) as a file on disk; nothing in this README was observed installing, loading or denying anything. That build does implement the Agent Plugins format: plugin.json occurs in the bundle, the installer recognises a package that carries one, and the legacy copy allow-list (POWER.md, mcp.json, steering/) is the else branch it no longer takes for this package. This caveat decides whether the Power installs at all, so read it as a bundle reading you should confirm against your own build — the check is at the end of this section.

A build predating the format installs this empty and says it succeeded. On the older 0.12.333 build (quality: stable, built 2026-06-10) the copy allow-list is the legacy one above, the string plugin.json does not occur in the extension bundle at all, and the copy routine swallows the missing-file error rather than raising it — so it reports a successful install of this Power and copies nothing: a silent total failure, not a partial one. That swallow is unchanged at 1.0.337; it was never fixed, it merely stopped applying to this package on a build new enough to recognise it.

The version to compare yourself against is not that one — it is the release that added the format. Kiro's public changelog dates Agent Plugin support to IDE 1.0.288, 7 Aug 2026: "Install powers aligned with the open Agent Plugin format from a local folder or GitHub URL." The 0.12.333 build predates that release by two months, and it is quoted here as the concrete evidence of what a pre-support build does, not as a threshold you can compare a version string to — the two numbers are not from the same series, so only the named release and the dates are comparable.

Verify against your own Kiro version before relying on it: after installing, confirm that ~/.kiro/powers/installed/tadeumendonca-skills/skills/ contains 15 directories. The installed/ segment is not optional and the last segment is the power name, which Kiro derives from the final path component of the URL above. If that directory does not exist or is empty, your build predates the format and nothing here is loaded.