Generate a client-facing project proposal from a validated discovery brief.
npx skills add https://github.com/TimeKast/AgendaInteligente --skill proposal-timekast
Please help me install this Agent Skill. Skill: proposal Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/roles/proposal Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill proposal-timekast
It helps translate a discovery brief into a polished, client-facing proposal that is easy to review and approval-ready, while keeping scope clear and avoiding technical language.
Run the proposal generation after providing a complete Discovery Brief and the project context file (glossary and client stakeholders) so the skill can produce docs/planning/01_PROPOSAL.md ready for client review.
High-intent search queries and answers about installing and using this skill.
To generate a client-facing project proposal, provide a validated discovery brief and client context to produce a structured, approval-ready document. The output defines objectives, user roles, MVP scope, planned evolution, and success criteria using business language without technical jargon.
Translating product discovery features into a non-technical proposal requires rewriting validated needs into actionable objectives and solutions. The document explicitly defines primary and secondary flows, MVP scope, and assumptions to manage client expectations using clear business language.
Yes, you need a complete discovery brief before generating MVP scope and planned evolution documents. The workflow enforces mandatory discovery coverage checks for ideas, users, and features to ensure required validation exists before producing the client-facing proposal.
Defining assumptions and risks improves client communication by forcing explicit boundary statements and validation guardrails within the proposal. This scope clarity manages client expectations effectively, ensuring the MVP and planned evolution phases are approval-ready and transparent.
Yes, you can include user roles and primary flows in a business-language proposal without technical jargon. The generation process rewrites technical discovery concepts into structured, non-technical document sections that clients can easily read, approve, and sign.
If your discovery context is missing required user or feature definitions, proposal generation will fail the mandatory pre-checks. The system enforces explicit validation guardrails to ensure complete discovery coverage exists before creating the structured client document.
VenTheZoneTransform user ideas into approved design specifications through iterative questioning.
prestariusApply standardized numbering scheme to Epics, User Stories, and Tasks in planning documents.
whawkinsivTurn vague product ideas into buildable specifications with user outcomes, screens, and edge cases.
echarabatiGenerate client-facing proposal documents from discovery briefs and client context.
