- Home
- Skills
- Business & Operations
- Client Brief to Project Blueprint
Works with the AI Agents you already use
Client Brief to Project Blueprint
Transforms messy client briefs and discovery notes into structured, professional project blueprints and risk registers.
$4.99
Client Brief to Project Blueprint
Example session with this skill installed
Here is a brief for a corporate website redesign. The client wants a new CMS, a blog, and a careers page. Deadline is 3 months. Budget is $20k. They need it to be mobile friendly.
- Read your context and instructions
- Compiled the client brief to
I have analyzed the brief for the corporate website redesign and generated a structured project blueprint.
Client Brief-to-Project Blueprint
1. Executive summary
- Client objective: Modernize corporate digital presence via a website redesign.
- Intended outcome: A mobile-friendly site with integrated CMS, blog, and careers functionality.
Major unknowns: Existing CMS data migration needs, specific third-party integrations, and brand asset availability.
2. Goals and success measures
- Stated Goal: Achieve mobile responsiveness. Metric: 100% pass rate on Google Mobile-Friendly test.
- Proposed Metric: CMS Page Load Speed. Target: Under 2 seconds (Requires client approval).
3. Scope
Included: UI/UX design, CMS implementation, Blog module, Careers portal development, Mobile optimization.
Excluded: Content writing, professional photography, SEO auditing, third-party recruitment software integration.
Constraints: $20k fixed budget, 3-month delivery window.
4. Requirements register
| ID | Requirement | Type | Priority | Status | Deliverable |
|---|---|---|---|---|---|
| REQ-01 | Mobile-friendly design | Design | Must | Confirmed | Responsive UI |
| REQ-02 | CMS Integration | Technical | Must | Confirmed | Backend System |
| REQ-03 | Careers Page | Functional | Should | Confirmed | Careers Portal |
5. Deliverables and acceptance criteria
| Deliverable | Components | Acceptance criteria | Dependencies |
|---|---|---|---|
| Responsive UI | Figma Mockups, CSS | Renders correctly on iOS Safari and Chrome Android | Brand style guide |
| CMS Handoff | Admin dashboard, Manual | User can edit blog posts without code | Hosting access |
6. Risk register
| Risk | Likelihood/impact | Evidence | Mitigation |
|---|---|---|---|
| Scope Creep | High/High | Vague "redesign" terms | Explicit exclusions list |
| Migration Delay | Medium/High | No mention of old data | Pre-discovery audit |
9. Missing information
- Blocking: What is the current CMS platform?
- High priority: Are there specific brand guidelines to follow?
- Useful later: Who will manage the blog content post-launch?
Next steps
- Send the "Missing Information" list to the client to clear blocking items.
- Confirm the proposed acceptance criteria for the mobile-friendly requirement.
- Validate if the $20k budget includes hosting fees and CMS licensing.
Connects securely to your tools. The creator never sees your data.
About this skill
Vague client briefs and informal discovery notes often lead to scope creep and missed deadlines. This skill bridges the gap between a messy intake process and a professional project plan. It extracts business logic, requirements, and constraints from raw text to produce a structured, client-ready blueprint.
What it does
- Extracts requirements by identifying business, functional, and technical needs from emails or RFPs.
- Defines deliverables with specific components, handoff formats, and definitions of done.
- Maps dependencies to highlight prerequisite tasks, client inputs, and third-party bottlenecks.
- Assesses risks by evaluating likelihood and impact, then providing mitigation and contingency plans.
- Prioritizes gaps by ranking missing information as blocking, high priority, or useful later.
How it works
- Provide a client brief, email thread, or discovery notes.
- The skill parses the text to separate confirmed facts from inferences and assumptions.
- It generates a comprehensive Markdown document following a standardized 12-section project structure.
- Review the generated risk register and requirements table to identify project blind spots.
Frameworks & tools
This skill is framework-agnostic and works with any text-based input from platforms like Slack, Gmail, or CRM discovery forms. It outputs structured Markdown compatible with GitHub, Notion, or project management tools.
Why this beats prompting it yourself
Writing a project plan manually often results in missed edge cases or vague acceptance criteria. This skill enforces a strict logic that separates assumptions from facts, ensuring you never commit to a deadline or budget based on incomplete data.
Use cases
- Freelance proposals to define exact scope and exclusions before signing a contract.
- Agency discovery to transform meeting notes into a professional requirement register.
- Internal planning to map out dependencies and risks for a new technical project.
- Scope control to document what is explicitly out of scope for a client.
Known limitations
Does not generate actual budget figures, calendar dates, or legal contract language. It cannot verify the technical feasibility of the client's requests.
Does not generate budget figures or calendar dates. Cannot verify technical feasibility. Output is not a legal contract.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 11 days ago
Permissions
No special permissions declared or detected