Slava Minamoto avatar

Slava Minamoto

Community

@skkap · Japan, Tokyo

25Followers
|
36Public Repos
|
5Published Skills

Slava Minamoto (skkap) publishes skills for pull-request shipping, feature planning, and project domain-model maintenance with decision records.

Skills Distribution
DomainDeveloper To...Feature Planning &.. (30%)Domain Modeling & .. (30%)Pull Request & Cod.. (25%)Decision Record Do.. (15%)

Agent Skills by Slava Minamoto

Showing 5 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Slava Minamoto

FAQPage Schema
What tasks can I accomplish with skkap's skills?

You can ship current work as a pull request with green local checks (fly), plan and scope features through structured decision questions (shape-it, shape-it-lite), and build or maintain a project's domain model and decision records (domain, domain-adopt).

Who are these skills designed for?

Software engineers and project maintainers who want disciplined pull-request shipping, upfront feature scoping, and explicit domain vocabulary management. They suit both codebases and document-based projects like knowledge vaults, research archives, or company records.

How does the fly skill ship a pull request?

Fly reads the repo's CHECKS.md (or derives checks when absent), branches off the default branch, runs the checks and fixes failures, commits, pushes, and opens or updates the PR. It finishes once the PR is open and does not wait on CI.

What is the difference between shape-it and shape-it-lite?

Shape-it reads and writes the project's domain model and decision records, so settled terms are never re-asked. Shape-it-lite is the stripped-down sibling for repos with no DOMAIN.md or docs/decisions/ — it reads no domain model and keeps everything in the plan file.

When should I use domain-adopt versus the domain skill?

Use domain-adopt only when explicitly asked to seed or bootstrap a domain model from existing scattered vocabulary; it rewrites CLAUDE.md in a one-off pass. Use domain for ongoing model maintenance — pinning terminology, resolving conflicts, and recording hard-to-reverse decisions.