mh-ms-file-engineer

Automated file generation in the MicroHard framework reads an approved artifact blueprint and generates files through a structured content creation and review process. It uses specialist sub-agents for different file types to maintain quality and consistency across the project lifecycle.

Blueprint-driven development enforces user sign-off by pausing the file engineering process at each stage. No file is written to disk without explicit user verification and approval, ensuring precision and preventing unauthorized changes to the project.

Trigger file engineering by saying 'ms build' or 'engineer the skill' in your MicroHard environment. Follow the interactive prompts to initiate the blueprint reading, content generation, and specialist sub-agent review stages for your project files.

Yes, file engineering in MicroHard requires specialist sub-agents to handle different file types within the generated blueprint. This approach maintains quality and consistency by leveraging specialized logic for each specific file format during the generation process.

No, this skill operates strictly within the context of a broader project lifecycle and requires a predefined, approved artifact blueprint. It reads the blueprint to generate files and cannot perform unstructured code generation without this foundational document.