yuxuanhui
91861565bb
- Introduced API guidelines for interface contracts and request handling. - Added design tokens usage guidelines for consistent styling across the project. - Established DTO guidelines for defining request parameters and response data types. - Created frontend structure guidelines to clarify directory organization and code placement rules. - Compiled a comprehensive frontend development guideline document covering various aspects of the development process. - Implemented quality guidelines to ensure code maintainability and adherence to best practices.
1.1 KiB
1.1 KiB
name, description
| name | description |
|---|---|
| pm-requirement-refine | Refine user-facing requirements from a PM perspective. Use when Codex needs to transform reviewed intake into traceable user requirement, requirement analysis, scenario analysis, user stories, acceptance criteria, and open questions. |
PM Requirement Refine
Refine a reviewed intake into PM-side requirement artifacts.
Inputs
- INTAKE.
- PM review note.
- Existing business context.
Process
- Write the user requirement in user-goal language.
- Extract business value, target users, constraints, and non-goals.
- Produce requirement analysis with assumptions, dependencies, and risks.
- Produce scenario analysis for main, alternative, exception, and boundary scenarios.
- Define acceptance criteria that can be verified later.
- Create traceability metadata for all generated artifacts.
Output
Generate or update:
- UR.
- RA.
- SA.
- Open question list.
Quality Bar
- Each requirement has a clear user or business value.
- Each scenario maps to at least one requirement.
- Each acceptance criterion is observable.
- Unknowns are not hidden inside polished prose.