Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsClient Project Planner
Turn approved client work into a sequenced delivery plan with owners, milestones, dependencies, and acceptance checks.
$9.99
Client Project Planner
Example session with this skill installed
Using this already-approved project scope: [paste proposal/SOW and known requirements, redact sensitive data], create an execution-ready plan for [project]. Team and capacity: [known or unknown]. Client dependencies, review timing, constraints, and target dates: [known or unknown]. Define outcomes and deliverables, workstreams, sequenced tasks with dependencies, owners only where confirmed, milestones without inventing dates, client inputs/approvals, risks and assumptions, QA/acceptance criteria, communication cadence, change control, and closeout. Flag blockers and contradictions. Preserve sold scope and label unknowns; do not invent commitments.
- Read your context and instructions
- Compiled the client project planner
Planning status
The approved scope describes a website redesign, but no team roster, approved deadline, capacity estimate, client review window, or named approver was supplied. Dates and individual owners remain TBD. Confirm them before making schedule commitments.
Outcomes and deliverables
- Outcome: deliver the website redesign defined in the approved scope.
Deliverables: use only the exact items listed in the signed scope; verify that source before adding pages, designs, content, implementation, testing, or handoff work.
Acceptance: map each deliverable to the agreement’s stated criteria. If criteria are missing, record an open decision rather than inventing a contractual standard.
Work breakdown and sequence
| Phase | Work | Dependency | Owner | Exit check |
|---|---|---|---|---|
| 1. Confirm readiness | Reconcile scope, exclusions, approver, dates, assets, access, and review process | Approved scope and kickoff decisions | Project lead TBD | Open questions have owners |
| 2. Discovery and inputs | Gather required content, brand materials, site context, and constraints | Client provides agreed inputs | Client lead TBD | Inputs support the first milestone |
| 3. Plan and design | Create in-scope structure and design deliverables | Discovery decisions and assets | Design owner TBD | Review package matches scope and criteria |
| 4. Build or implement | Implement approved designs and in-scope functions | Design approval and required access | Delivery owner TBD | Ready for agreed QA |
| 5. QA and client review | Test against agreed criteria, track defects, collect authorized feedback | Build complete and test environment | QA/approver TBD | Critical findings resolved or accepted |
| 6. Handoff and closeout | Deliver approved artifacts, documentation, and support handoff | Acceptance and access decisions | Project lead TBD | Deliverables and open items documented |
This is a planning sequence only. Remove phases outside the sold scope and add work only when approved.
Dependencies and open decisions
- Who is authorized to approve design, scope questions, and final acceptance?
- Which materials and access are needed for the first milestone, and who will provide them? Use a secure least-privilege process; never put credentials in the plan.
- What review windows and response expectations are agreed?
- Which third-party, content, technical, accessibility, privacy, or security dependencies are in scope?
- Which milestone dates are contractually agreed, and what capacity supports them?
- How should requested changes be assessed, approved, and scheduled under the existing agreement?
Risk and control log
| Risk or assumption | Impact | Response | Status |
|---|---|---|---|
| Approver or review window unknown | Rework or waiting | Confirm authority and review process at kickoff | Open |
| Required assets or access incomplete | Dependent tasks may wait | Request only required items and track owner/date | Open |
| Scope or acceptance criteria unclear | Dispute or scope drift | Reconcile against signed agreement and seek written decision | Open |
| Capacity or deadline unverified | Unrealistic schedule | Estimate after owners and availability are confirmed | Open |
Governance
Use an agreed status cadence covering completed work, next steps, client decisions, blockers, risks, and change requests. Keep a decision log with date, decision, authorized approver, impact, and source. Do not treat silence as approval. Route out-of-scope requests through the agreed change process before adding work.
Next steps
At kickoff, confirm the authoritative scope, approver, owner roster, capacity, review windows, first milestone, required inputs, and change process. Create dated tasks only from verified facts and baseline them with the client. No delivery date or capacity claim is made here.
Connects securely to your tools. The creator never sees your data.
About this skill
Client Project Planner
Turn work that has already been sold into an execution-ready plan. Convert an approved proposal, quote, contract, statement of work, discovery notes, client requirements, and known constraints into outcomes, deliverables, workstreams, tasks, milestones, dependencies, owners, checkpoints, risks, communication cadence, quality checks, acceptance criteria, change control, handoff, and closeout.
Preserve the agreed scope and commercial baseline. Separate delivery work from client decisions, reviews, waiting time, and third-party dependencies. Make owners and assumptions visible, identify blockers before work starts, and plan a practical sequence instead of returning a flat task list. Include status reporting, decision and risk logs, escalation paths, QA, testing, launch, support, and acceptance steps as appropriate.
Do not invent contract terms, approvals, team members, dates, budgets, capacity, dependencies, technical facts, stakeholder authority, or integrations. Flag ambiguity and seek an authorized decision. This skill does not guarantee delivery dates or replace legal, financial, engineering, or security professionals. Human review controls commitments and changes.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed 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 scanned
Verified clean 9 days ago
- Passed all security checks, Safe to install