open-plugin

Decompose a domain into bounded contexts, aggregates, entities, value objects, and domain events with ubiquitous-language naming, mapping bounded contexts to candidate microservice boundaries. Use whenever the user wants to decompose a domain, split a system into bounded contexts, identify aggregates / value objects / domain events, define clean domain entities, draw clear boundaries, or plan a monolith-to-microservices breakup. Also use when an already-decomposed domain has evolved and the user wants to update, extend, re-run, or "read existing and update" an existing `docs/domain` model rather than start over — re-running delta-merges into the existing docs (stable ids, preserves human edits, flags drops) instead of overwriting. Works from a prose domain/requirements description, not existing code. Trigger even when the user never says "DDD", as long as they are carving a domain into boundaries, modelling entities/aggregates/events, or updating a model they already have.

Structure a clear, verifiable /goal from rough user input through guided interview. Use this skill whenever the user says "define goal", "tạo goal", "/goal", "goal cho task này", "I want to do X" (where X is complex/multi-step), "structure this task", "make this into a goal", or when you detect the user has a vague multi-step objective that would benefit from structured goal definition. Also trigger when the user pastes a wall of requirements and needs them organized into a runnable goal. Covers all task types: implementation, exploration/research, audit/review, and refactoring.

Install a skill from a GitHub URL into the user's personal skills directory (~/.claude/skills/). Use whenever the user says "chom <url>", "install this skill from github", "add/import/grab this skill", or pastes a GitHub URL that clearly points at a SKILL.md folder — handle both full-repo skills and subfolder skills like https://github.com/github/awesome-copilot/tree/main/skills/azure-devops-cli. Also handles optional description optimization of the newly installed skill when the user explicitly asks for it afterward. Trigger even when the user doesn't say the word "chom" as long as the intent is "pull a skill from GitHub into my skills folder".

This skill should be used when the user asks to "analyze business requirements", "do business analysis", "create a requirements document", "map business processes", "write user stories", "feasibility assessment", "stakeholder analysis", "data modelling", "process improvement", "acceptance criteria", "business case", "gap analysis", "as-is to-be analysis", "business modelling", "requirements elicitation", "impact analysis", or mentions business analyst / business analysis work. Guides developers, analysts and aspiring BAs through business analysis tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Analyze → Design → Deliver & Validate), inline coaching, and competency assessment. Do NOT use for: solution architecture, infrastructure design, product roadmap management, or code-level implementation decisions.

This skill should be used when the user asks to "define IT strategy", "create IT governance", "write an IT roadmap", "do IT leadership planning", "IT governance framework", "review my IT strategy", "CIO task", "IT portfolio", "IT operating model", "IT investment", "digital transformation", "technology strategy", "IT leadership", "service management", "IT budget", "vendor management", "IT risk", "information management", "IT roadmap", or mentions IT leadership or CIO work. Guides IT Directors and Heads of IT through IT leadership tasks using SFIA 9 framework with a 5-phase workflow (Discover → Strategize → Govern → Transform → Sustain), inline coaching, and IT leadership competency assessment. Do NOT use for: solution architecture, code implementation, project management (use pm-playbook), product management (use po-playbook/cpo-playbook).

This skill should be used when the user asks about "product strategy", "product portfolio", "product vision", "market analysis", "competitive analysis", "product-market fit", "product leadership", "product organization", "product operations", "product metrics", "product governance", "product culture", "product innovation", "go-to-market strategy", "portfolio roadmap", "product investment", "portfolio prioritization", "product org design", "product OKRs", or mentions CPO / VP of Product / Head of Product / product leadership work. Guides senior PMs, VPs of Product and aspiring CPOs through strategic product leadership tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Prioritize → Plan → Deliver & Learn), inline coaching, and competency assessment. Do NOT use for: day-to-day PO backlog management (use po-playbook), solution architecture (use sa-playbook), IT strategy (use cio-playbook).

This skill should be used when the user asks to "define a technology vision", "create a technology strategy", "write a tech roadmap", "do technology evaluation", "build vs buy analysis", "engineering culture", "platform strategy", "tech stack assessment", "engineering excellence", "technical debt strategy", "R&D strategy", "innovation pipeline", "technology due diligence", or mentions technology leadership work. Guides engineering leads and VPs through CTO tasks using SFIA 9 framework with a 5-phase workflow (Discover → Envision → Build → Scale → Evolve), inline coaching, and technology leadership assessment. Do NOT use for: IT operations/service management (use cio-playbook), solution architecture (use sa-playbook), product management (use cpo-playbook).

This skill should be used when the user asks to "create an enterprise architecture", "define a business capability model", "write architecture principles", "do enterprise architecture", "build a technology roadmap", "architecture governance", "architecture review board", "IT strategy", "target architecture", "reference architecture", "TOGAF", "architecture standards", "capability model", "business architecture", "business capability", or mentions enterprise architecture work. Guides solution architects and tech leads through EA tasks using SFIA 9 framework with a 5-phase workflow (Discover \u2192 Define \u2192 Design \u2192 Govern \u2192 Evolve), inline coaching, and architecture assessment. Do NOT use for: solution-level design (use sa-playbook), code implementation, CI/CD pipeline setup, or project management.

This skill should be used when the user asks to "create a project plan", "project management", "programme management", "portfolio management", "risk register", "stakeholder management", "project governance", "RAID log", "project charter", "milestone planning", "resource planning", "change management", "benefits realization", or mentions project delivery work. Guides team leads and coordinators through project delivery tasks using SFIA 9 framework with a 5-phase workflow (Discover -> Define -> Plan -> Execute -> Close & Learn), inline coaching, and project delivery competency assessment. Do NOT use for: solution architecture, product roadmap, code implementation, or CI/CD pipeline setup.

This skill should be used when the user asks to "create a product roadmap", "prioritize the backlog", "define product vision", "write user stories", "do product management", "product strategy", "release planning", "stakeholder management", "feasibility assessment", "customer journey", "product metrics", "OKRs", "value proposition", "sprint planning", "backlog grooming", "backlog refinement", "product discovery", or mentions product owner / product management work. Guides developers, PMs and aspiring POs through product management tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Prioritize → Plan → Deliver & Learn), inline coaching, and competency assessment. Do NOT use for: solution architecture, infrastructure design, CI/CD pipeline setup, or code-level implementation decisions.

This skill should be used when the user asks to "design a system", "create an architecture", "write an ADR", "do solution architecture", "architect a solution", "review my architecture", "SA task", "stakeholder analysis", "trade-off analysis", "C4 diagram", "non-functional requirements", "NFR", "architecture decision record", or mentions solution architecture work. Guides developers and tech leads through SA tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Design → Decide → Deliver), inline coaching, and architecture assessment. Do NOT use for: code-level design patterns, CI/CD pipeline setup, or infrastructure provisioning (Terraform/Pulumi).

This skill should be used when the user asks to "create a test plan", "test strategy", "write test cases", "test automation", "acceptance testing", "quality assurance", "QA", "testing approach", "risk-based testing", "regression testing", "performance testing", "test management", or mentions testing work. Guides developers and QA through testing tasks using SFIA 9 framework with a 5-phase workflow (Discover → Plan → Execute → Evaluate → Improve), inline coaching, and testing competency assessment. Do NOT use for: code-level unit test implementation, CI/CD pipeline setup, or infrastructure provisioning.

Use this skill when the user wants to create a PRD from scratch, explore a problem space, run Design Thinking, or transform pain points into structured product requirements. Guides users through Empathize, Define, Ideate, Prototype, and PRD compilation to produce a vbounce-compatible Product Requirements Document. Triggers: "design thinking", "create PRD", "explore problem", "pain point", "empathize", "user research", "ideation", "from scratch PRD", "start from problem", "I have a problem but no PRD". Do NOT use for existing PRDs (use vbounce directly), general brainstorming outside product development, or UX design/wireframing.

Use this skill when the user wants to run a V-Bounce SDLC cycle, start a vbounce workflow, or manage a structured software development lifecycle with the V-Bounce framework. Orchestrates 12 specialized agents through phases: Requirements, Design, Contracts, Implementation (unified TDD), Review, and Deployment with mixed-model assignment, per-phase specialized QG agents, unified TDD flow, tech-aware context injection, state management, contract validation, and quality gates at every transition. Triggers: "start vbounce cycle", "run sdlc pipeline", "resume vbounce", "APPROVED", "CHANGES REQUESTED", "START BUGFIX", "START CR", "tech-aware", "TDD flow". Do NOT use for general code review, testing, design, or implementation tasks outside the V-Bounce framework.