drewbarontin
5 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
drewbarontiniequilio-frame
Define a software problem and its desired outcome before committing to a solution; use for a rough request, proposed feature, bug, or unclear issue.
- 導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日
drewbarontiniclassify-work
Give product work clear coordinates by identifying its Type, Impact, Product Landscape location, work form, and routing state. Use when an item needs to become legible before prioritization, grouping, or movement through a Work Registry.
- 導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日
drewbarontinicompare-perspectives
Engage meaningfully distinct perspectives to expose assumptions, tensions, tradeoffs, and blind spots, then integrate them into better judgment. Use when a consequential question benefits from genuine difference, not generic expert aggregation or consensus.
- 導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日
drewbarontinimap-product-anatomy
Turn a software product surface or flow into a compact, versionable anatomy of Screens, Components, Actions, States, and Flows using Anatomica. Use when product structure needs to become inspectable before pixels, code, or detailed implementation.
- 導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日
drewbarontinimap-shape
Turn a fuzzy product problem or opportunity into a coherent, valuable, simplified, and sequenced shape of work. Use when product work needs boundaries and vertical slices before implementation planning.
- 導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日