guild-context-assemble

To assemble per-specialist context bundles, you combine universal principles, role-specific standards, and task-specific plan details into a single markdown file for each lane. This ensures consistent guidance before dispatch.

A 3-layer context bundle is a briefing format that combines universal guild principles, role-dependent standards, and task-dependent plan details. It guides dispatch by providing comprehensive, reproducible context for each specialist lane.

You manage token budgets by enforcing a reproducibility policy during context assembly, sourcing only essential universal principles, role-specific standards, and task-specific references to generate concise markdown bundles for subagents.

You need to generate role-dependent context files once a plan is approved and before dispatching tasks. This ensures each specialist receives lane-specific standards and task details required for execution.

Yes, context assembly works by sourcing from wiki context, guild principles, and plan-derived data. It extracts project overviews, role standards, and task-specific lane blocks to create the final briefing bundle.

The best way to ensure consistent guidance is to automate context assembly, combining scattered wiki entities, decisions, and plan blocks into a single markdown bundle per specialist. This prevents inconsistent guidance during dispatch.