prompt-shaper

Name: prompt-shaper
Availability: InStock
Author: LazyIsEfficient

Convert vague engineering requests into ready-to-execute task briefs.

15|3|Updated Apr 9, 2026

Search Tags:#workflow #templates #scoping #intake #task-brief #prompt-shaping

Ready to run

npx skills add https://github.com/LazyIsEfficient/agentic-os --skill prompt-shaper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prompt-shaper
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/prompt-shaper
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill prompt-shaper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Shapes vague requests into well-scoped briefs to align downstream agents, reducing back-and-forth and misinterpretation.

Core Features & Use Cases

Template-driven intake: automatically selects the correct brief type (multi-repo, single-repo, investigation, or bugfix) and loads the corresponding template.
Structured questioning: uses a 2-round approach to batch and resolve load-bearing gaps via the provided interview checklist.
Actionable output: returns a fully formed task brief ready for task breakdown or direct execution.

Quick Start

Provide a vague engineering request and your current working directory; I will generate a complete, ready-to-execute task brief.

Frequently Asked Questions about prompt-shaper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn a vague engineering request into an actionable task brief?▼

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.

What is the best way to scope a software engineering task for downstream agents?▼

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.

How does template-driven intake work for engineering task breakdown?▼

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.

Do I need to provide my working directory to generate a task brief?▼

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.

What types of engineering briefs can be created for task execution?▼

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.