moai-workflow-design-context

To consolidate design briefs into a token-budgeted workflow context, this skill reads files from the .moai/design directory and applies priority-based truncation to produce a compact context block for injection. It sequences spec, system, research, and pencil-plan content while honoring design_docs configuration limits.

When design briefs exceed the token budget, priority-based truncation is automatically applied to the loaded content. The system reads spec, system, research, and pencil-plan files in parallel, truncating lower-priority information to ensure the consolidated context block fits within the configured limits.

To load updated design briefs into the Moai workspace context, the skill reads human-authored research, system, spec, and pencil-plan files from the .moai/design directory. It processes these files in parallel and returns a designed context block ready for immediate orchestrator injection.

Yes, the Moai workflow context skill supports parallel file reading for design docs. It simultaneously loads spec, system, research, and pencil-plan files from the .moai/design directory before applying token-budget-aware truncation and generating the final context block with optional warnings.

Yes, you can use design_docs configuration to control workflow context generation. The skill explicitly honors these configuration settings when loading and sequencing content from the .moai/design directory, ensuring the generated context block aligns with your specified priority and token budget constraints.

A key limitation when truncating design briefs is potential information loss from priority-based truncation during token budget enforcement. While the skill consolidates the files and returns a context block ready for injection, it provides optional warnings to alert you when content has been truncated.