Skip to main content

Frequently Asked Questions

Everything you need to know about the MySpec file bundle and workflow.

What is constitution.md?

Non-negotiable principles and constraints that guide all subsequent phases. This file acts as the project's 'supreme law', defining tech stack choices (e.g., 'Must use TypeScript'), architectural patterns, and coding standards that the AI must adhere to.

What is requirements.md?

A detailed functional specification generated in Phase 1. We use the EARS+ (Easy Approach to Requirements Syntax) format to ensure requirements are unambiguous, testable, and complete. It defines 'what' the system does without prescribing 'how'.

What is design.md?

A comprehensive solution design document generated in Phase 2. It translates the requirements into technical implementation details, including database schemas, API endpoints, component hierarchies, and system diagrams (Mermaid.js).

What is tasks.md?

An implementation plan generated in Phase 3. It breaks down the approved design into granular, sequential tasks. Each task is scoped small enough to be easily completed by an AI coding agent or a human developer.

Still have questions?

Join our community or reach out to us directly.