vibedev-specs-mcp
Version:
MCP server for vibedev specs workflow - AI-powered development workflow from requirements to code
29 lines (22 loc) • 910 B
JavaScript
export async function requirementsConfirmed(params) {
const { session_id, feature_name } = params;
console.error(`[MCP] Requirements confirmed for feature: ${feature_name}`);
return `# ✅ Requirements Gathering Completed
## Generated Requirements Document:
📄 ".vibedev/specs/${feature_name}/requirements.md"
The requirements document contains complete user stories and EARS-format acceptance criteria.
## Next Stage: Design Document (3/5)
### Workflow Progress:
- [x] 1. Goal Collection ✅
- [x] 2. **Requirements Gathering** ✅
- [ ] 3. **Design Document** ← Next Stage
- [ ] 4. Task Planning
- [ ] 5. Task Execution
Now please call \`vibedev_specs_design_start\` to begin the technical design stage.
**Session Information**:
- Session ID: \`${session_id}\`
- Feature Name: \`${feature_name}\`
- Requirements: ✅ Completed`;
}
//# sourceMappingURL=requirements_confirmed.js.map