Yuto Tanaka

You can run a full spec-driven development cycle: generate EARS requirements, produce architecture and design documents, create implementation tasks, dispatch and review subtasks, validate designs and implementations, detect requirement gaps, and verify completion claims using command outputs and exit codes.

Software developers practicing specification-first development with Kiro, plus individual users managing personal email, calendar, and Todoist tasks. The Japanese writing skills target authors drafting or revising Japanese technical books, chapters, and explanatory articles.

The use-spark skill requires the spark binary installed to access email, calendar, and contact data. The Kiro skills operate on project JSON metadata, Markdown specs, YAML configurations, and repository state. Todoist and writing skills need no external binaries.

kiro-validate-design checks design documents against architecture standards, kiro-validate-impl verifies boundary integrity across feature tasks, kiro-review confirms implementations match approved specs via diff analysis, and kiro-verify-completion confirms claims using recent command outputs and exit codes.

japanese-tech-writing defines formatting rules (one sentence per line, footnotes, columns), paragraph structure, and redundancy elimination. cognitive-rhythm-writing governs pacing through cognitive-mode shifts, paragraph density waves, and post-writing mechanical inspection procedures.