prd-agent-brief

To generate a sub-agent brief, provide the task, role, and project scope. The system collects required slots like file ownership, token budgets, and success criteria, then fills a fixed prompt template to output a ready-to-submit invocation brief.

A sub-agent invocation brief is a formal prompt that binds an orchestrator to safety constraints and ownership contracts. You need one when spawning implementation, validator, or learner sub-agents within a build loop to ensure traceability and safe execution.

You enforce token budgets and file permissions by generating a formal brief that validates file ownership, sets permission envelopes, and defines runaway mitigation rules before the sub-agent is spawned in the build loop.

Yes, you can use sub-agent briefs for validator and learner sub-agents. The brief generation process applies to any sub-agent invocation within a build loop, ensuring all required metadata and safety contracts are present.

The brief generation requires all mandatory slots—including task, role, may_write, may_not_touch, and context_pack—to be present before composition. It cannot generate a valid brief if any required metadata field is missing or invalid.