Huruikagi
- 37 skills
- 0 followers
- 8 hours ago last updated
- ▌ Kiro Debug · huruikagiInvestigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
- ▌ Kiro Review · huruikagiReview a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
- ▌ Kiro Verify Completion · huruikagiVerify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
- ▌ Sb Dev Sync Docs · huruikagi bundleKeep SpecBind's English and Japanese public documentation aligned and the Japanese copy natural and readable. Use for changes or language-quality reviews under docs/en or docs/ja, bilingual navigation, or public documentation URLs; exclude English-only generated reference pages and internal repository documentation.
- ▌ Sb Dev Forward Test · huruikagiRun the behavioral forward tests for SpecBind's embedded skills against a fixture project, using subagents with no prior context. Use when a product-managed skill changed materially, before a release, or when a decision's effect on agent behavior needs checking.
- ▌ Sb Plan · huruikagi bundlePlan active Spec work through Requirements, Design, Contract Review, and Tasks, run one explicitly requested planning phase for one named Spec, or prepare explicitly scoped project shared Contracts. Ordinary Spec planning uses one named Spec or explicit all-Spec scope.
- ▌ Sb Adopt · huruikagiEstablish Specs from an explicitly selected existing implementation, then retire this temporary adoption Skill after successful finalization.
- ▌ Sb Debug · huruikagiUse directly when the user asks why a Task failed or cannot be implemented. Establish the root cause, categorize it, and return a next action. Read-only; never starts implementation or applies the fix.
- ▌ Sb Drive · huruikagi bundleDrive the active milestone through every safe reachable planning, implementation, and validation action. Park branch-local attention and continue elsewhere; stop before release execution.
- ▌ Sb Dev Merge Dependabot · huruikagiReview and integrate Dependabot pull requests in Huruikagi/specbind one at a time, with current-branch checks, main CI verification, and affected dependency or toolchain validation. Use when asked to handle or merge SpecBind Dependabot PRs; do not use for dependency upgrades that have no Dependabot PR.
- ▌ Sb Status · huruikagi bundleReport where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done.
- ▌ Sb Release · huruikagi bundleClose the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.
- ▌ Sb Dev Resolve Dogfooding · huruikagiTriage and resolve open dogfooding-labeled Issues in Huruikagi/specbind through contract analysis, product implementation, verification, commit and push, and evidence-backed Issue disposition. Use when asked to work through SpecBind dogfooding findings; do not use for general Issue triage.
- ▌ Sb Steering · huruikagiMaintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.
- ▌ Sb Configure · huruikagi bundleConfigure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.
- ▌ Sb Discovery · huruikagi bundleTurn a change request or Source Collection into confirmed Spec and milestone boundaries.
- ▌ Sb Implement · huruikagi bundleImplement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented.
- ▌ Sb Review Task · huruikagiJudge whether one implemented task is done correctly, from the actual diff and the approved requirements, design, and plan.
- ▌ Sb Gap Analysis · huruikagiCompare what a change needs against what the repository already provides, and record the findings worth keeping. Informs the decision; does not make it.
- ▌ Sb Contract Review · huruikagiJudge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.
- ▌ Sb Validate Design · huruikagiIndependently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
- ▌ Sb Verify Completion · huruikagiConsequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
- ▌ Sb Validate Implementation · huruikagiUse only when every Task for a named Spec is complete and the user explicitly asks for lifecycle validation against the active Requirement IDs that records completion on GO. For a consequence-free claim check, use sb-verify-completion.
- ▌ Kiro Impl · huruikagi bundleImplement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
- ▌ Kiro Steering · huruikagiMaintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
- ▌ Kiro Discovery · huruikagiEntry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
- ▌
- ▌ Kiro Spec Batch · huruikagiCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
- ▌
- ▌ Kiro Spec Tasks · huruikagiGenerate implementation tasks from requirements and design. Use when creating actionable task lists.
- ▌ Kiro Spec Design · huruikagiGenerate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
- ▌
- ▌ Kiro Validate Gap · huruikagiAnalyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
- ▌ Kiro Validate Impl · huruikagiValidate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
- ▌ Kiro Steering Custom · huruikagiCreate custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
- ▌ Kiro Validate Design · huruikagiInteractive technical design quality review and validation. Use when reviewing design before implementation.
- ▌ Kiro Spec Requirements · huruikagiGenerate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.