prompt-shaper

To turn a vague engineering request into an actionable task brief, provide the initial request and your working directory. The system applies a structured intake process with a guided interview checklist to resolve gaps and deliver a ready-to-execute brief.

Scoping a software engineering task for downstream agents is best handled by selecting the appropriate template, such as multi-repo or bugfix, and asking load-bearing questions. This shapes vague requests into precise briefs, reducing misinterpretation and alignment issues.

Template-driven intake for engineering task breakdown works by automatically selecting the correct brief type, like investigation or single-repo, and loading the corresponding template. It uses a two-round approach to batch and resolve load-bearing gaps before execution.

Yes, you need to provide your current working directory alongside the vague engineering request. This allows the system to generate a complete, ready-to-execute task brief tailored to your specific project context.

The types of engineering briefs that can be created for task execution include multi-repo, single-repo, investigation, and bugfix briefs. Each brief type corresponds to a specific template loaded during the structured intake process.