Transforms vague project ideas into structured technical requirements and project briefs.
The Requirement Crystallizer (arm) is designed to bridge the gap between initial fuzzy concepts and actionable technical documentation. It follows the Opus Crystallization Protocol to systematically extract requirements, constraints, style preferences, and key concepts from the user. By driving the conversation through structured probing and decision checkpoints, it ensures that project goals are clearly defined before any architecture or implementation begins. The final output is a standardized brief saved to your documentation directory, serving as a single source of truth for subsequent development phases.
Key Features
01Structured trade-off checkpoints to resolve project ambiguities
027 GitHub stars
03Automated brief synthesis using standardized Markdown templates
04Standardized output to PROCESS_DOCS for seamless workflow integration
05Systematic extraction of requirements, constraints, and style preferences
06Phase-based task tracking for transparent requirement gathering
Use Cases
01Standardizing project documentation for team handoffs and design phases
02Defining project scope and non-goals before starting system architecture
03Converting a high-level feature idea into a detailed product specification
