From vamfi-software-consultancy
This skill should be used when the user asks to "write a proposal", "respond to this RFP", "draft a statement of work", "create a pitch document", "write an executive summary", or needs to produce a client-facing document to win or structure an engagement.
npx claudepluginhub vamfi/vamfi-plugins --plugin vamfi-software-consultancyThis skill uses the workspace's default tool permissions.
Produce compelling, client-centric proposals and RFP responses that win engagements by demonstrating deep understanding of the client's problem and a credible path to solving it.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Produce compelling, client-centric proposals and RFP responses that win engagements by demonstrating deep understanding of the client's problem and a credible path to solving it.
Great proposals lead with the client's problem, not the vendor's credentials. Apply this skill to produce structured proposals or RFP responses that are tailored, evidence-based, and commercially clear.
Proposal (proactive): VAMFI initiates based on a qualified opportunity. Structure around win themes.
RFP Response (reactive): Client has issued a formal tender. Must address all stated requirements and often follow a specified structure. If the client has specified a structure, follow theirs exactly — do not impose VAMFI's structure.
Before writing, identify 2-3 win themes — the core reasons VAMFI should win this engagement:
Every section of the proposal should reinforce at least one win theme.
The executive summary is the most-read section. Structure it as:
Standard proposal structure:
# Proposal: [Initiative Title]
Prepared for: [Client Name]
Prepared by: VAMFI Software
Date: [YYYY-MM-DD]
## Executive Summary
## Understanding Your Requirements
[Paraphrase requirements — shows listening, not boilerplate]
## Our Proposed Approach
### Phase 1: [Name] — [Duration]
[What happens, who is involved, what is produced]
### Phase 2: [Name] — [Duration]
...
## Why VAMFI
[Credentials, experience, differentiators — keep brief, 1 page max]
## Commercial Proposal
| Item | Approach | Rate/Cost | Duration | Total |
|---|---|---|---|---|
Assumptions:
- [List commercial assumptions]
Exclusions:
- [What is NOT included]
## Next Steps
1. [Specific action — e.g., "Discovery workshop on [date]"]
2. [Decision expected by [date]]
For T&M engagements:
For fixed-price:
For outcome-based:
When responding to a formal RFP:
references/win-theme-frameworks.md — How to identify and reinforce win themesassets/proposal-template.md — Full blank proposal templateassets/rfp-compliance-matrix.md — Compliance matrix template