agent-factory

Automated specialized agent file generation extracts functional domains from plan_analysis.json and outputs structured .agent.md files with defined roles, tool access, reference docs, and hard constraints for each domain.

Generating domain-specific agent files requires analysis/plan_analysis.json and SYSTEM_MANIFEST.md as inputs to extract agent domains and map functional boundaries for the generated system architecture.

Plan analysis maps to specialized agent roles by extracting functional domains from plan_analysis.json, then generating individual .agent.md files that define specific scope, tool access, reference documentation, and hard constraints for each domain.

Generated agent files are stored as .github/agents/*.agent.md files, accompanied by a .github/agents/README.md that documents the collection of specialized agents created for the system architecture.

Generating specialized agents requires SYSTEM_MANIFEST.md as a mandatory input alongside analysis/plan_analysis.json, meaning the agent generation process cannot proceed without these prerequisite files defining the system architecture.

Defining agent scope and tool access from a project plan is best handled by automating specialized agent file generation, which parses plan analysis to produce .agent.md files with clear scope boundaries, reference docs, and hard constraints per domain.