moai-workflow-design-context

Inject design briefs into a workflow context by loading files from a design directory and applying priority-based truncation. This approach preserves critical spec content while discarding less essential notes to stay within token budget limits.

Priority-based truncation evaluates design sources like spec, system, and research files, preserving high-priority content while discarding less essential notes. This deterministic process ensures critical information remains available when the token budget is exceeded.

Yes, you can load design briefs from a custom directory by invoking the context loader standalone with a directory override. This bypasses the automatic workflow trigger, allowing targeted content assembly.

Manual token budget configuration is unnecessary because the context assembly implements config-driven token budgeting. It automatically applies truncation rules during batched parallel reads of design files to ensure deterministic operation.

The best way to consolidate research and spec files is through batched parallel reads that assemble content into a single context. This method injects structured pencil-plan and system data into prompts for downstream agents.

Spec details drop during injection when token budgets are exceeded and truncation rules prioritize other content. Adjust the configuration to assign higher priority to spec files to prevent losing critical information.