vamfi-plugins

This skill should be used when the user asks to "use the VAMFI templates", "get the proposal template", "find the PRD template", "use the HLD template", "load the runbook template", "access artifact templates", or needs a blank template for any VAMFI consultancy document.

This skill should be used when the user asks to "shape stories", "create a backlog", "break this epic into stories", "write user stories with acceptance criteria", "define the product backlog", "estimate stories", or needs to convert a PRD or delivery plan into an executable sprint backlog.

This skill should be used when the user asks to "implement this feature", "write the code for this story", "execute this implementation plan", "make this code change", "add this functionality", or needs hands-on code implementation following a VAMFI implementation plan.

This skill should be used when the user asks to "review this code", "review the PR", "check code quality", "refactor this module", "improve this code", "run a code review", or needs systematic review of recently written or changed code before it merges.

This skill should be used when the user asks to "optimise costs", "reduce cloud spend", "improve performance", "fix slow queries", "analyse FinOps", "reduce latency", "optimise infrastructure", "right-size resources", or needs to improve the efficiency of a running system.

This skill should be used when the user asks to "assess the current architecture", "document the existing system", "analyse the codebase", "identify technical debt", "review the legacy system", "produce a current-state report", or needs to understand what exists before designing a target architecture.

This skill should be used when the user asks to "create a delivery plan", "build a roadmap", "plan the phases", "define milestones", "map the critical path", "estimate the timeline", or needs a structured phased plan for delivering an initiative.

This skill should be used when the user asks to "create a deployment plan", "plan the release", "design the rollout strategy", "define rollback procedures", "plan the go-live", "create a release checklist", or needs to plan how a feature or service will be deployed to production.

This skill should be used when the user asks to "write a PRD", "draft product requirements", "create a requirements document", "define features and NFRs", "write user stories for a product", or needs to produce a structured Product Requirements Document from discovery findings or a product brief.

This skill should be used when the user asks to "run a health check", "assess the engagement", "how healthy is this project", "retrospective", "check delivery health", "review team performance", "assess client satisfaction", or needs a structured assessment of an ongoing consulting engagement.

This skill should be used when the user asks to "create an implementation plan", "define the branching strategy", "specify coding patterns", "plan how to implement this feature", "set coding guardrails", or needs a detailed technical plan before writing code.

This skill should be used when the user asks to "run a postmortem", "write an incident report", "document this outage", "conduct a blameless retrospective for this incident", "analyse the root cause", or needs to learn from a production incident.

This skill should be used when the user asks to "design integrations", "create an API design", "define the event catalogue", "design the integration architecture", "document API contracts", "design the event-driven architecture", or needs to specify how systems communicate with each other.

This skill should be used when the user asks to "define NFRs", "set performance targets", "define SLAs and SLOs", "analyse capacity requirements", "specify scalability targets", "define reliability requirements", or needs to translate business expectations into measurable non-functional requirements.

This skill should be used when the user asks to "map this process", "create an AS-IS process map", "design the TO-BE process", "build a RACI matrix", "identify process bottlenecks", "document a business process", or needs to analyse and improve an existing workflow.

This skill should be used when the user asks to "qualify this opportunity", "assess this inbound request", "evaluate this client brief", "score this RFP", "check if we should pursue this", "write an opportunity brief", or needs to determine whether to pursue a sales or consulting engagement.

This skill should be used when the user asks to "create a regression plan", "plan regression testing", "identify regression risks", "plan test automation", "assess flaky tests", "determine regression scope for this release", or needs to protect against regressions during a release or refactoring exercise.

This skill should be used when the user asks to "run discovery", "facilitate a discovery session", "create a discovery document", "map stakeholders", "build an assumption register", "define success metrics", "plan discovery interviews", or needs to structure the initial research phase of an engagement.

This skill should be used when the user asks to "create a runbook", "write operational procedures", "define SLO alerting", "design the on-call playbook", "review service operability", "create incident response procedures", or needs to prepare a service for production operations.

This skill should be used when the user asks to "review security architecture", "run a threat model", "produce a security review", "check for security risks", "review OWASP compliance", "assess security controls", "run a pre-production security gate", or needs security analysis at any stage of the SDLC — not just at the end.

This skill should be used when the user asks to "create a spec", "break this into tasks", "spec out this feature", "write a spec for this story", "convert requirements to tasks", "plan this initiative", or needs to turn any natural language requirement into a structured, agent-executable task breakdown following the 2026 Spec Kit pattern.

This skill should be used when the user asks to "design the target architecture", "create an HLD", "produce a high-level design", "design the future state", "create architecture decision records", "choose a tech stack", or needs to define what the system should look like after transformation.

This skill should be used when the user asks to "generate test cases", "write tests for this feature", "create test scenarios", "suggest edge cases", "generate unit tests", "write E2E tests", "create acceptance tests", or needs specific test cases for a story, endpoint, or module.

This skill should be used when the user asks to "create a test strategy", "define the testing approach", "plan our test levels", "set quality gates", "define test coverage targets", "create a test plan for this feature", or needs to define how an initiative will be tested end-to-end.

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.

This skill should be used when the user asks to "load a team pack", "bootstrap a team", "start a team from config", "use a saved team", "load team-pack", or wants to create a Claude Code team from a folder-based team pack configuration.

This skill should be used when the user asks to "list team packs", "show saved teams", "validate a team pack", "check team pack structure", "team pack details", "what teams do I have", or needs to manage, inspect, or validate team pack configurations.

This skill should be used when the user asks to "save the current team", "export team config", "capture team setup", "create team pack from running team", "save team as reusable pack", or wants to persist a running Claude Code team as a portable folder configuration.

This skill activates when the user asks about "architecture extraction", "story context", "dev notes", "source citations", "context bridge", "relevant architecture", or needs guidance on how BMAD extracts and embeds relevant architecture context into story files for developers.

This skill activates when the user discusses BMAD methodology, project phases, agent coordination, phase gates, workflow routing, or asks about "which BMAD agent", "what phase am I in", "BMAD workflow", "phase transition", "agent handoff". Provides knowledge about BMAD's 4-phase methodology and 9 specialized agents.

This skill activates when the user asks about "story creation", "sprint planning", "story development cycle", "story validation", "code review workflow", "dev story", "create next story", "story template", or needs guidance on BMAD's implementation workflow patterns.

This skill activates when the user asks about "business strategy", "business model", "pricing strategy", "go-to-market", "competitive analysis", "market positioning", "revenue model", "value proposition", "competitive moat", "market entry", "growth strategy", "unit economics", or needs guidance on strategic business decisions, market analysis, or business model design.

This skill activates when the user asks about "financial model", "revenue projections", "cash flow", "P&L", "profit and loss", "break-even analysis", "unit economics", "budget", "financial forecast", "burn rate", "runway", "margins", "cost structure", "financial planning", "pricing model", or needs guidance on financial analysis, business math, or financial decision-making.

This skill activates when the user asks about "team management", "hiring", "scaling operations", "OKRs", "KPIs", "processes", "organizational design", "company culture", "leadership", "delegation", "remote team", "performance management", "project management", "agile", "sprint planning", "meeting cadence", "one-on-ones", or needs guidance on building teams, running operations, or organizational effectiveness.

This skill activates when the user asks about "startup", "fundraising", "pitch deck", "MVP", "minimum viable product", "venture capital", "angel investors", "seed round", "Series A", "cap table", "term sheet", "product-market fit", "pivoting", "co-founder", "startup metrics", "runway", "burn rate", or needs guidance on launching, funding, or growing an early-stage company.