Draft a lightweight user flow document with problem, actors, and approval sections.
npx skills add https://github.com/Alfie728/my-skills --skill user-flow-alfie728
Please help me install this Agent Skill. Skill: user-flow Source: https://github.com/Alfie728/my-skills/tree/main/user-flow Command: npx skills add https://github.com/Alfie728/my-skills --skill user-flow-alfie728
Draft a lightweight, non-technical user flow document after kickoff calls to align business and avoid miscommunication. The document is readable by product leads and non-technical stakeholders.
Draft the user flow using the provided template and fill in the feature details to generate the initial document.
High-intent search queries and answers about installing and using this skill.
To draft a user flow document for leadership review, capture the problem, rationale, actors, and flow steps in a lightweight template to ensure business alignment before architecture begins. This delivers a readable, non-technical artifact for stakeholder feedback.
The best way to align non-technical stakeholders is creating a post-kickoff user flow artifact that defines the user experience and business rationale in a leadership-friendly format, preventing miscommunication between product leads and business teams.
No, a business-friendly user flow template does not capture technical architecture details. It focuses on the problem, rationale, actors, approval processes, and flow steps to provide a definitive description of the business logic and user experience.
You need to create a post-kickoff artifact for business alignment immediately after kickoff calls and before architecture planning. It ensures product leads and leadership agree on the user experience and business rationale before engineering resources are committed.
Yes, you can use a user flow document to get formal approval from product leaders. The generated artifact includes specific approval processes and is designed to be review-ready, allowing leadership to provide direct feedback and align on the user experience.
mutsumi-yamamotoDetect input types, profile data, extract document information, and update analysis_context.md.
indykishIdentify gaps and risks in engineering plans across architecture, data flow, and test coverage.
omeraltnPrioritize product backlog items using RICE and value-effort scoring.
partme-aiGenerate UML, C4, and architecture diagrams from PlantUML syntax.
