proposal

To convert a vague request into implementation-ready specs, the proposal Skill explores unclear inputs with targeted clarification questions, then generates formal specifications, acceptance criteria, and task breakdowns from the conversation context.

Generating developer-ready proposals from a brainstorming session is done by summarizing the conversation context and passing a structured Plan summary with a Context payload to a subagent for deterministic artifact creation.

Yes, you can automatically create task breakdowns and supporting documentation from direct user input. The proposal Skill processes the input, explores missing details, and outputs comprehensive change proposals with all required artifacts.

No, producing test requirements through the proposal generation process does not require manual handoffs. It automatically converts conversation plans into formal specs, ticket breakdowns, and test requirements directly.

The clarification process for incomplete change requests works by automatically exploring vague inputs with targeted questions before generating final artifacts, ensuring the resulting specifications and tasks are accurate and unambiguous.

You need to launch a subagent for proposal artifact creation when you have a summarized conversation plan and context payload ready, requiring the subagent to process these inputs for deterministic downstream generation of specifications and supporting documentation.