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.0 KiB
1.0 KiB
name, description
| name | description |
|---|---|
| se-requirement-review | Review PM-side requirement artifacts from an SE perspective. Use when Codex needs to evaluate whether UR, requirement analysis, and scenario analysis are ready to become engineering objective requirements and development requirements. |
SE Requirement Review
Review PM artifacts for engineering readiness.
Inputs
- UR.
- RA.
- SA.
- PM open questions and review notes.
Process
- Check whether business requirements can be translated into engineering outcomes.
- Identify missing non-functional requirements.
- Identify interface, data, dependency, integration, permission, migration, and compatibility concerns.
- Identify architectural or delivery risks.
- Mark unresolved questions that block OR or DR.
Output
Produce an SE review note with:
- Engineering readiness decision.
- Blocking questions.
- Required technical clarifications.
- Risk list.
- Suggested OR/DR breakdown.
Decision
Use one of:
ready-for-or-drready-with-risksblocked