// 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 "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 "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.
| name | Current State Assessment |
| description | 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. |
| version | 1.0.0 |
Systematically assess an existing system or codebase to produce a clear picture of the current architecture, capabilities, and technical debt. This assessment drives the gap analysis that informs the target architecture.
No target architecture is designed in a vacuum. This skill documents what exists today — its strengths, its limitations, and the debt that will impede change — so that the target architecture is grounded in reality.
Catalogue what exists:
Read the codebase (if available) using Glob and Read to supplement what the user provides.
Identify the dominant architectural pattern:
Note whether the pattern is intentional or has evolved organically.
Rate current capabilities:
| Capability | Current State | Maturity | Notes |
|---|---|---|---|
| Scalability | [description] | Low/Med/High | |
| Observability | [description] | Low/Med/High | |
| Security | [description] | Low/Med/High | |
| Testability | [description] | Low/Med/High | |
| Deployability | [description] | Low/Med/High | |
| Developer Experience | [description] | Low/Med/High |
| Item | Category | Severity | Impact on Change | Remediation Approach | Effort |
|---|---|---|---|---|---|
| [debt item] | Architecture/Code/Data/Ops | Critical/High/Med/Low | [how it blocks progress] | [recommendation] | S/M/L |
Categories:
Compare current state to typical requirements for the target state:
| Capability | Current | Required for Target | Gap | Priority |
|---|---|---|---|---|
| [capability] | [current level] | [required level] | [description of gap] | High/Med/Low |
Produce a Current State Assessment document with:
references/technical-debt-patterns.md — Common technical debt patterns and remediation strategiesassets/current-state-template.md — Blank assessment template