target-state-definition

Designs target architecture and component mappings for migration projects.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill target-state-definition-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: target-state-definition
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/target-state-definition
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill target-state-definition-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migration projects often fail or drift because teams lack a clear, documented vision of the end state. This Skill produces a structured target architecture definition so every subsequent migration step has a concrete design to follow. ## Core Features & Use Cases - Target Architecture Design: Creates architecture diagrams, component mapping matrices, and technology stack specifications aligned with platform best practices. - Design Decision Documentation: Records key architectural decisions with alternatives considered, rationale, and trade-offs in a decisions log. - Use Case: When migrating a Java 11 monolith to Java 21 with Spring Boot 3, use this Skill to produce a design_target_architecture.md that maps each existing component to its target form, specifies versions, and documents decisions like adopting virtual threads. ## Quick Start Analyze my current codebase and assessment report, then create a target architecture design document for migrating to the new platform.

Frequently Asked Questions about target-state-definition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a target architecture for a migration project?▼

Start by analyzing the current architecture with file and code inspection, then research target platform best practices. Document the result as an architecture diagram, a component mapping matrix, a technology stack with versions, and a design decisions log.

What should a migration design document include?▼

A migration design document should include an executive summary, target architecture diagram, component mapping matrix, architectural patterns with rationale, technology stack versions, and a decisions log covering alternatives and trade-offs.

Does this Skill modify my existing code during design?▼

No. The Skill operates in read-only analysis mode, examining existing code and configurations without modifications. It produces only design documentation and diagrams, not code changes.

What inputs are required to design a target state?▼

The Skill requires an assessment report describing current architecture and dependencies, a migration plan with scope and constraints, and target platform requirements covering best practices, compliance, and performance targets.

When is target state definition not the right step?▼

Skip detailed target design when the migration strategy is retire or retain, since no new architecture is needed. It is most valuable for replatform, refactor, and rehost scenarios where the end state must be specified.