VAMFI

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.

Systematic methodology for identifying, capturing, and documenting reusable patterns from implementations. Enables automatic learning and knowledge-core.md updates. Claude invokes this after successful implementations to preserve institutional knowledge.

Active context curation to fight context rot. Curates what goes into limited context window from constantly evolving information universe. 39% improvement, 84% token reduction.

Systematic validation methodology for ResearchPacks and Implementation Plans. Provides scoring rubrics and quality gates to ensure outputs meet standards before proceeding to next phase. Prevents garbage-in-garbage-out scenarios.

Systematic approach for creating minimal-change, reversible implementation plans. Claude invokes this skill when transforming requirements/research into executable blueprints. Emphasizes simplicity, safety, and clear verification steps.

Systematic approach for gathering authoritative, version-accurate documentation. Claude invokes this skill when research is needed before implementation. Ensures truth over speed while achieving both.

This skill should be used when the user asks to "create a skill", "forge a skill", "generate a skill", "build a Claude skill", "make a new skill", or wants to understand skill creation methodology. Provides research-grounded methodology for creating high-quality Claude Code skills with official documentation verification.