all publishers

Huruikagi

@huruikagi source repo

40 published skills

  1. ▌
    Kiro Debug 2 · huruikagi
    Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
    2 repo stars
  2. ▌
    Kiro Review 2 · huruikagi
    Review 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.
    2 repo stars
  3. ▌
    Kiro Verify Completion 2 · huruikagi
    Verify 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.
    2 repo stars
  4. ▌
    Kiro Debug · huruikagi
    Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
    2 repo stars
  5. ▌
    Kiro Review · huruikagi
    Review 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.
    2 repo stars
  6. ▌
    Kiro Verify Completion · huruikagi
    Verify 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.
    2 repo stars
  7. ▌
    Sb Dev Sync Docs · huruikagi bundle
    Keep 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.
    2 repo stars
  8. ▌
    Sb Dev Forward Test · huruikagi
    Run 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.
    2 repo stars
  9. ▌
    Sb Plan · huruikagi bundle
    Plan 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.
    2 repo stars
  10. ▌
    Sb Adopt · huruikagi
    Establish Specs from an explicitly selected existing implementation, then retire this temporary adoption Skill after successful finalization.
    2 repo stars
  11. ▌
    Sb Debug · huruikagi
    Use 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.
    2 repo stars
  12. ▌
    Sb Drive · huruikagi bundle
    Drive the active milestone through every safe reachable planning, implementation, and validation action. Park branch-local attention and continue elsewhere; stop before release execution.
    2 repo stars
  13. ▌
    Sb Dev Merge Dependabot · huruikagi
    Review 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.
    2 repo stars
  14. ▌
    Sb Status · huruikagi bundle
    Report 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.
    2 repo stars
  15. ▌
    Sb Release · huruikagi bundle
    Close the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.
    2 repo stars
  16. ▌
    Sb Dev Resolve Dogfooding · huruikagi
    Triage 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.
    2 repo stars
  17. ▌
    Sb Steering · huruikagi
    Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.
    2 repo stars
  18. ▌
    Sb Configure · huruikagi bundle
    Configure 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.
    2 repo stars
  19. ▌
    Sb Discovery · huruikagi bundle
    Turn a change request or Source Collection into confirmed Spec and milestone boundaries.
    2 repo stars
  20. ▌
    Sb Implement · huruikagi bundle
    Implement 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.
    2 repo stars
  21. ▌
    Sb Review Task · huruikagi
    Judge whether one implemented task is done correctly, from the actual diff and the approved requirements, design, and plan.
    2 repo stars
  22. ▌
    Sb Gap Analysis · huruikagi
    Compare what a change needs against what the repository already provides, and record the findings worth keeping. Informs the decision; does not make it.
    2 repo stars
  23. ▌
    Sb Contract Review · huruikagi
    Judge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.
    2 repo stars
  24. ▌
    Sb Validate Design · huruikagi
    Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
    2 repo stars
  25. ▌
    Sb Verify Completion · huruikagi
    Consequence-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.
    2 repo stars
  26. ▌
    Sb Validate Implementation · huruikagi
    Use 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.
    2 repo stars
  27. ▌
    Kiro Impl · huruikagi bundle
    Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
    2 repo stars
  28. ▌
    Kiro Steering · huruikagi
    Maintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
    2 repo stars
  29. ▌
    Kiro Discovery · huruikagi
    Entry 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.
    2 repo stars
  30. ▌
    Kiro Spec Init · huruikagi
    Initialize a new specification with detailed project description
    2 repo stars
  31. ▌
    Kiro Spec Batch · huruikagi
    Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
    2 repo stars
  32. ▌
    Kiro Spec Quick · huruikagi
    Quick spec generation with interactive or automatic mode
    2 repo stars
  33. ▌
    Kiro Spec Tasks · huruikagi
    Generate implementation tasks from requirements and design. Use when creating actionable task lists.
    2 repo stars
  34. ▌
    Kiro Spec Design · huruikagi
    Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
    2 repo stars
  35. ▌
    Kiro Spec Status · huruikagi
    Show specification status and progress
    2 repo stars
  36. ▌
    Kiro Validate Gap · huruikagi
    Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
    2 repo stars
  37. ▌
    Kiro Validate Impl · huruikagi
    Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
    2 repo stars
  38. ▌
    Kiro Steering Custom · huruikagi
    Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
    2 repo stars
  39. ▌
    Kiro Validate Design · huruikagi
    Interactive technical design quality review and validation. Use when reviewing design before implementation.
    2 repo stars
  40. ▌
    Kiro Spec Requirements · huruikagi
    Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
    2 repo stars