YasuakiOmokawa
- 21 skills
- 0 followers
- 19 hours ago last updated
- ▌ QA UI · yasuakiomokawaVerifies an implemented UI when the request provides observable checks, expected states, an accessible rendered page, and permitted interactions.
- ▌ Build Poc · yasuakiomokawaUse when a technical choice or feasibility must be decided through a PoC or minimal experiment against success criteria in an executable environment.
- ▌ Create Pr · yasuakiomokawaCreate 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.
- ▌ Model Data · yasuakiomokawaUse 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.
- ▌ Verify Plan · yasuakiomokawaUse when an implemented change must be verified against a plan or acceptance criteria before it can be considered complete.
- ▌ Dry Ssot Text · yasuakiomokawaConsolidates duplicated reader-facing procedures when a canonical document and in-scope documents are identified, while preserving audience-specific differences.
- ▌ Apply Findings · yasuakiomokawaApplies review findings when a request authorizes mechanically safe edits or asks for concrete edit candidates without changing files.
- ▌ Create Commits · yasuakiomokawaTurn 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.
- ▌ Build Prototype · yasuakiomokawaUse 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.
- ▌ Map User Stories · yasuakiomokawaTurn supplied product evidence into a user story map when user value, stories, executable tasks, and delivery order must be made traceable.
- ▌ Mece Plan Review · yasuakiomokawaCompare 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 · yasuakiomokawaUse 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.
- ▌ Create Jira Issues · yasuakiomokawaCreate 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.
- ▌ Extract Figma Spec · yasuakiomokawaUse 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.
- ▌ Purge Private Vocab · yasuakiomokawaReplaces private vocabulary in authorized reader-facing documents when supplied definitions make the intended meaning checkable for the target audience.
- ▌ Set Jira Story Points · yasuakiomokawaSet 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.
- ▌ Express Intent In Code · yasuakiomokawaClarifies intent in existing code when unclear names, responsibilities, comments, or lint suppressions need behavior-preserving cleanup.
- ▌ Ground Design In Codebase · yasuakiomokawaReviews a proposed design boundary before implementation when relevant specifications and existing code can provide concrete evidence about responsibilities and risk.
- ▌ Translate To Vision Story · yasuakiomokawaUse 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.
- ▌ Define Acceptance Criteria · yasuakiomokawaConvert an existing plan or specification into observable acceptance criteria when success, failure, boundary, or non-impact behavior must be made decidable.
- ▌ Prepare Plan For Implementation · yasuakiomokawaPrepare 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.