weapp-requirements

Structure raw feature requests into INVEST-oriented User Story documents for WeChat mini programs.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/hekinami/weapp-dev-workflow --skill weapp-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weapp-requirements
Source: https://github.com/hekinami/weapp-dev-workflow/tree/main/skills/weapp-requirements
Command: npx skills add https://github.com/hekinami/weapp-dev-workflow --skill weapp-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague feature requests into structured User Story documents so teams can align on scope, value, and delivery before implementation begins.

Core Features & Use Cases

  • Requirements Discovery: It guides discussion around user roles, goals, business value, inputs, outputs, edge cases, and acceptance criteria.
  • Architecture Alignment: It checks whether the request fits the existing architecture and highlights when a design review is needed.
  • User Story Generation: It produces a consistent User Story document with IDs, priority, status, business flow, data needs, interface needs, and related docs.
  • Use Case: A product owner describes a new mini program feature, and the Skill converts that idea into a review-ready User Story file for the team.

Quick Start

Provide the feature request and any relevant architecture context, and ask this Skill to draft a User Story document for the target function.

Frequently Asked Questions about weapp-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user stories for WeChat mini program features?

Generating user story documents for WeChat mini programs involves structuring raw feature requests with IDs, priorities, business flows, data needs, interface requirements, edge cases, and INVEST-oriented acceptance criteria.

What is architecture alignment in product requirement discovery?

Architecture alignment in requirement discovery evaluates whether a proposed feature fits the existing WeChat mini program architecture and highlights when a formal design review is needed before implementation.

How do I turn vague feature requests into acceptance criteria?

Turning vague feature requests into acceptance criteria requires applying the INVEST principle to structure user goals, business value, inputs, outputs, and edge cases into testable conditions within a user story document.

Can I use this for existing WeChat mini program projects or only new ones?

You can use it for both new and existing WeChat mini program projects, as it supports feedback-driven refinement and architecture-aligned requirement discovery for ongoing product planning.

What is the best way to structure product documentation for mini program development?

The best way to structure product documentation is to generate a consistent user story file containing IDs, priority, status, business flow, data needs, interface needs, and linked design documentation.

Why do I need INVEST-oriented user stories for product planning?

INVEST-oriented user stories ensure your product planning produces independent, negotiable, valuable, estimable, small, and testable features so teams can align on scope and delivery before implementation begins.