specify

acornsoft's avatarfrom acornsoft

Define functional/non-functional specs in MacroFlow.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

The Specify skill automates the transition from abstract requirements to concrete technical execution. It specializes in defining comprehensive functional and non-functional specifications, software architectures, and data models. By producing structured documentation and architecture diagrams, it ensures that engineering teams have a precise, actionable roadmap for implementation while maintaining technical accuracy and consistency.

Use Cases

  • Translating high-level business requirements into detailed technical specification documents (Markdown/JSON) for development teams.
  • Designing system architectures and data structures, including API definitions and interface models, for new software modules.
  • Generating Architectural Decision Records (ADR) to document technical trade-offs and design choices during the system design phase.
  • Validating proposed technical designs against project constraints and constitutional requirements to ensure architectural integrity.
namespecify
descriptionDefine functional/non-functional specs in MacroFlow.

Specify Skill

Overview

The Specify phase defines technical specifications and details based on clarified requirements. It produces precise, actionable specs for implementation.

Purpose

  • Define technical requirements
  • Specify architectures and designs
  • Detail interfaces and data models
  • Prepare for planning

Inputs

  • Clarified requirements
  • Constitutional constraints

Process

  1. Define technical specs
  2. Specify design patterns and architectures
  3. Detail APIs and data structures
  4. Validate against constraints

Outputs

  • Technical specification document
  • Architecture diagrams
  • Detailed requirements

Grok Integration

Use Grok for precise specification generation. Temperature: 0.3 for technical accuracy.

Next Phase

Proceed to Plan when specs are complete.

Instructions

  1. Produce structured spec (Markdown + JSON).
  2. Include ADR-style trade-offs.

Examples

  • Input: Requirements.
  • Output: Detailed specs.

Learned Patterns

  • Incorporate flow network.