YasuakiOmokawa
@YasuakiOmokawa
Public Skills
express-intent-in-code
by YasuakiOmokawa
Reduces comments in existing code by moving their intent into names, structure, types, and checks when a file or diff carries comments that restate or stand in for what the code could express itself.
apply-findings
by YasuakiOmokawa
Applies review findings when a request authorizes mechanically safe edits or asks for concrete edit candidates without changing files.
build-poc
by YasuakiOmokawa
Use when a technical choice or feasibility must be decided through a PoC or minimal experiment against success criteria in an executable environment.
define-acceptance-criteria
by YasuakiOmokawa
Convert an existing plan or specification into observable acceptance criteria when success, failure, boundary, or non-impact behavior must be made decidable.
mece-plan-review
by YasuakiOmokawa
Compare a plan and acceptance criteria with specification and code evidence when a MECE coverage review or an explicitly authorized review update is requested.
create-design-doc
by YasuakiOmokawa
Use when an approved plan and evidence of both feasibility and codebase fit—from a PoC and prototype or equivalent evidence—must become a Design Doc at a specified or derived destination for implementation decisions.
ground-design-in-codebase
by YasuakiOmokawa
Reviews a proposed design boundary before implementation when relevant specifications and existing code can provide concrete evidence about responsibilities and risk.
model-data
by YasuakiOmokawa
Use when business requirements must be modeled against available schema or SQL to produce a consistent data model, optional DBML, and evidence-backed findings on data design, entity relationships, schema consistency, or SQL anti-patterns.
dry-ssot-text
by YasuakiOmokawa
Consolidates duplicated reader-facing procedures when a canonical document and in-scope documents are identified, while preserving audience-specific differences.
build-prototype
by YasuakiOmokawa
Use when an approved PoC or equivalent evidence exists and real code must test whether the selected approach fits the codebase's responsibilities, conventions, and contracts.
qa-ui
by YasuakiOmokawa
Verifies an implemented UI when the request provides observable checks, expected states, an accessible rendered page, and permitted interactions.
create-pr
by YasuakiOmokawa
Create or update the pull request associated with the current branch when the user asks to open it, revise its content, or explicitly make it reviewable.
prepare-plan-for-implementation
by YasuakiOmokawa
Prepare an existing plan for implementation when it already has valid acceptance criteria and a ready MECE review, by ordering concrete work and writing a same-plan verification mapping; do not use it to implement the plan.
purge-private-vocab
by YasuakiOmokawa
Replaces private vocabulary in authorized reader-facing documents when supplied definitions make the intended meaning checkable for the target audience.
create-jira-issues
by YasuakiOmokawa
Create Jira issues when the user explicitly asks to file listed, approved stories or tasks in a specified project and issue type, with per-item keys and failures.
set-jira-story-points
by YasuakiOmokawa
Set Jira Story Points when the user provides explicit issue-key-to-point mappings and asks to update those issues, with requested and confirmed values reported per issue.
create-commits
by YasuakiOmokawa
Turn the current branch's uncommitted or unpublished changes into commits whose boundaries a reviewer reads in order, when the user asks to commit, split, or restructure local history before publishing it.
extract-figma-spec
by YasuakiOmokawa
Use when supplied or retrievable Figma evidence must be decomposed into atomic checks and compared with an identified implementation for specified frames, states, or components in a design-difference table.
translate-to-vision-story
by YasuakiOmokawa
Use when creating a vision-linked article draft from project evidence for a target audience and goal, or revising an existing evidence-based draft under an approved direction; the vision may be supplied or configured.
verify-plan
by YasuakiOmokawa
Use when an implemented change must be verified against a plan or acceptance criteria before it can be considered complete.
map-user-stories
by YasuakiOmokawa
Turn supplied product evidence into a user story map when user value, stories, executable tasks, and delivery order must be made traceable.