vamfi-software-consultancy

Design the solution architecture for an initiative. Produces current-state assessment, target HLD, integration design, NFR analysis, security review, and Architecture Decision Records.

Run a full discovery session for a new product, feature, or transformation initiative. Produces a Discovery Document, stakeholder map, assumption register, and first-draft PRD.

Run the complete VAMFI 8-stage consulting pipeline end-to-end. Each stage produces artifacts and waits for human approval before proceeding. Use for new engagement kickoffs or full initiative reviews.

Produce an implementation plan with branching strategy, coding patterns, and guardrails. Optionally execute code changes and request multi-agent code review.

Generate a delivery plan, phased roadmap, and shaped backlog with epics and stories. Uses the spec-driven-planning skill to break the initiative into measurable, agent-executable tasks.

Run lead qualification for an inbound opportunity. Analyses the request, assesses strategic fit, budget reality, timeline, risks, and produces an opportunity brief with a recommended proposal outline.

Produce a deployment plan, operational runbook, and DevSecOps pipeline design for releasing a feature or service to production.

Ongoing operational support — cost and performance optimisation, incident postmortems, engagement health checks, and continuous improvement planning.

Create a test strategy, generate test cases, and produce a regression plan. Covers all test levels from unit through E2E, with AI-generated edge cases.

Use this agent when the user needs to run discovery, write a PRD, map business processes, define requirements, create user stories, or bridge business needs with technical solutions. Examples: <example> Context: User wants to run discovery on a new product idea user: "Run Discovery on this new product idea and produce a PRD." assistant: "I'll use the business-analyst agent to run structured discovery and produce a PRD with goals, user flows, and NFRs." <commentary> Discovery and PRD production is the Business Analyst's primary function. </commentary> </example> <example> Context: User needs to map an existing process user: "Map the current state of our customer onboarding process and identify improvement opportunities." assistant: "I'll use the business-analyst agent to produce an AS-IS process map with a pain-point heatmap and TO-BE recommendations." <commentary> Process mapping is a core BA skill — triggering this agent. </commentary> </example> <example> Context: User has vague requirements that need structuring user: "We want to improve our reporting. Can you help turn this into proper requirements?" assistant: "I'll use the business-analyst agent to elicit, structure, and document your reporting requirements as a PRD." <commentary> Turning vague briefs into structured requirements is a classic BA task. </commentary> </example>

Use this agent when the user needs a retrospective, engagement health check, continuous improvement planning, relationship review, or wants to assess delivery quality and team velocity. Examples: <example> Context: User wants to run a sprint retrospective user: "Run a retrospective on our last sprint and identify improvements." assistant: "I'll use the client-success-manager agent to facilitate a structured retrospective and produce an improvement backlog." <commentary> Retrospective facilitation is a core Client Success Manager function. </commentary> </example> <example> Context: User wants to assess overall engagement health user: "How healthy is this engagement? What should we improve?" assistant: "I'll use the client-success-manager agent to run an engagement health check across delivery, quality, team, and relationship dimensions." <commentary> Engagement health assessment is a primary CSM responsibility. </commentary> </example>

Use this agent when the user needs a deployment plan, CI/CD pipeline design, operational runbook, SRE practices, infrastructure design, or incident response procedures. Examples: <example> Context: User needs to plan a production deployment user: "DevOps Lead: propose a deployment plan and runbook for this service." assistant: "I'll use the devops-sre-lead agent to produce a deployment plan with rollout strategy, rollback criteria, and operational runbook." <commentary> Deployment planning and runbook creation are core DevOps/SRE Lead functions. </commentary> </example> <example> Context: User needs CI/CD pipeline designed user: "Design a CI/CD pipeline for our Node.js monorepo with security gates." assistant: "I'll use the devops-sre-lead agent to design a DevSecOps pipeline with quality gates, security scanning, and deployment automation." <commentary> CI/CD pipeline design with DevSecOps integration is a key DevOps Lead output. </commentary> </example>

Use this agent when the user needs domain modelling, bounded context mapping, ubiquitous language definition, vertical-specific architecture patterns, or Domain-Driven Design guidance. Examples: <example> Context: User needs domain modelling for a complex business domain user: "Help me model the domain for our insurance claims processing system." assistant: "I'll use the domain-architect agent to map bounded contexts, aggregates, and define the ubiquitous language for insurance claims." <commentary> Domain modelling and DDD are the Domain Architect's speciality. </commentary> </example> <example> Context: User is designing a system with complex business rules user: "Our payment orchestration has very complex state transitions. How should we model this?" assistant: "I'll use the domain-architect agent to design the domain model with aggregates, domain events, and state machine diagrams." <commentary> Complex business domain with state machines warrants domain architecture expertise. </commentary> </example>

Use this agent when the user needs to qualify an inbound opportunity, draft a proposal, respond to an RFP, assess strategic fit, or kick off a new client engagement. Examples: <example> Context: User has received an inbound request from a potential client user: "Engagement Manager: qualify this inbound request email and suggest a proposal outline." assistant: "I'll use the engagement-manager agent to assess this opportunity and produce an Opportunity Brief." <commentary> User is explicitly invoking the Engagement Manager role to qualify an opportunity — this agent owns stage 1 of the pipeline. </commentary> </example> <example> Context: User wants to respond to an RFP user: "We've received an RFP for a digital transformation programme. Help me build a response." assistant: "I'll use the engagement-manager agent to structure your RFP response with win themes, solution overview, and commercial approach." <commentary> RFP response is a core Engagement Manager output — invoking this agent. </commentary> </example> <example> Context: User wants to start a new engagement from scratch user: "We're starting a new engagement with a fintech client. Where do we begin?" assistant: "I'll use the engagement-manager agent to run the qualify-opportunity skill and map out the engagement kickoff." <commentary> New engagement kickoff is the Engagement Manager's primary trigger. </commentary> </example>

Use this agent when the user wants to run the full 8-stage VAMFI consulting pipeline, orchestrate handoffs between stages, track which stages have been completed, or resume an in-progress engagement. Examples: <example> Context: User wants to run the complete pipeline end-to-end user: "Run the full VAMFI pipeline for this new product initiative." assistant: "I'll use the pipeline-orchestrator agent to manage the complete 8-stage engagement pipeline with checkpoints between each stage." <commentary> Full pipeline orchestration is the primary function of this meta-agent. </commentary> </example> <example> Context: User wants to check where they are in the pipeline user: "Where are we in the engagement pipeline? What stage are we on?" assistant: "I'll use the pipeline-orchestrator agent to assess the produced artifacts and tell you exactly which stages are complete and what comes next." <commentary> Pipeline state assessment and next-stage guidance is a key orchestrator function. </commentary> </example> <example> Context: User wants to resume a paused engagement user: "We paused the engagement at architecture. Resume from where we left off." assistant: "I'll use the pipeline-orchestrator agent to load the existing artifacts, brief you on the current state, and continue from Stage 3." <commentary> Engagement resumption requires the orchestrator to read context and continue correctly. </commentary> </example>

Use this agent when the user needs a test strategy, test cases, regression plan, quality gates, or test automation guidance. Examples: <example> Context: User needs a test strategy for a new feature set user: "QA Lead: create a test strategy and initial test cases for this feature set." assistant: "I'll use the qa-lead agent to produce a test strategy covering all test levels and generate test cases with AI-suggested edge cases." <commentary> Test strategy and case generation are the QA Lead's primary outputs. </commentary> </example> <example> Context: User has a failing test suite to triage user: "Our test suite is slow and flaky. Help us build a regression plan." assistant: "I'll use the qa-lead agent to produce a regression plan with flaky test identification and automation ROI assessment." <commentary> Regression planning and test quality improvement are core QA Lead responsibilities. </commentary> </example>

Use this agent when the user needs a security architecture review, threat modelling, compliance assessment, shift-left security integration, secrets audit, or security controls checklist — at ANY stage of the pipeline. Examples: <example> Context: User needs a security review of their architecture user: "Security Lead: review this architecture design for security risks." assistant: "I'll use the security-compliance-lead agent to run a threat model and produce a security architecture review with controls checklist." <commentary> Security architecture review is the primary function of this cross-cutting agent. </commentary> </example> <example> Context: User is about to deploy and needs a security gate check user: "We're about to go live. Run a pre-production security checklist." assistant: "I'll use the security-compliance-lead agent to run the pre-production security gate covering secrets, dependencies, auth, and compliance." <commentary> Pre-production security gates are a key scenario for the Security Lead — shift-left means security at every stage. </commentary> </example> <example> Context: User needs compliance guidance user: "We need to be GDPR compliant. What do we need to address in our architecture?" assistant: "I'll use the security-compliance-lead agent to map GDPR requirements to architectural controls and produce a compliance gap analysis." <commentary> Compliance mapping to architecture is a core Security Lead responsibility. </commentary> </example>

Use this agent when the user needs to design a target architecture, assess the current state, produce HLD/LLD documents, make technology decisions, or create Architecture Decision Records. Examples: <example> Context: User wants architecture designed for a new system user: "Solution Architect: design target architecture for this repo + requirements in claude.md." assistant: "I'll use the solution-architect agent to assess the current state and produce a target HLD with ADRs." <commentary> Target architecture design is the Solution Architect's primary function. </commentary> </example> <example> Context: User needs a technology decision documented user: "We need to choose between PostgreSQL and MongoDB for this use case. Help me decide and document it." assistant: "I'll use the solution-architect agent to evaluate the options and produce an Architecture Decision Record." <commentary> Technology decisions with formal ADR documentation are core to the SA role. </commentary> </example> <example> Context: User has legacy system to modernise user: "Assess our current monolith and design a migration path to microservices." assistant: "I'll use the solution-architect agent to run a current-state assessment and design the target architecture with a phased migration plan." <commentary> Legacy assessment and modernisation architecture is a key SA scenario. </commentary> </example>

Use this agent when the user needs a delivery plan, epic/story breakdown, implementation guidance, coding patterns, technical decision support, or spec-driven task planning. Examples: <example> Context: User needs a delivery plan for an initiative user: "Tech Lead: generate a delivery plan and break into epics/stories with estimates." assistant: "I'll use the tech-lead agent to run spec-driven planning and produce a phased delivery plan with shaped stories." <commentary> Delivery planning and story shaping are the Tech Lead's primary outputs. </commentary> </example> <example> Context: User needs implementation guidance for a specific feature user: "How should we implement the real-time notification system? What's the branching strategy and tech approach?" assistant: "I'll use the tech-lead agent to produce an implementation plan with tech choices, branching strategy, and a step-by-step checklist." <commentary> Implementation planning and technical decision-making are core Tech Lead functions. </commentary> </example> <example> Context: User needs stories broken down from a PRD user: "We have a PRD for the checkout flow. Can you shape this into stories with acceptance criteria?" assistant: "I'll use the tech-lead agent to shape the PRD into an epic with stories, acceptance criteria, and T-shirt estimates." <commentary> Story shaping from PRDs is a key Tech Lead activity that warrants this agent. </commentary> </example>

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.

2 hooks across 2 events