メニュー
Use when a project has Architecture data that needs migrating to fine-grained entities (Decisions, Invariants, Components, Dependencies). Guides the agent through reading, mapping, confirming, and executing the migration with user oversight.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user's prompt is delivered outside the execution context of an existing Jumbo goal, the prompt is imbued with an objective that is not already defined as a Jumbo goal.
Use when a Jumbo-managed agent file tells the agent to bootstrap the session. Runs Jumbo's session router only when the agent has not already received a routed Jumbo command.
Use when an agent needs to discover Jumbo command syntax after session routing. Directs command discovery through CLI help instead of static command catalogs.
Use when implementation discovers durable project context that must be recorded in Jumbo. Captures decisions, components, dependencies, relations, guidelines, and invariants during the work.
Use when the user corrects an approach, constraint, workflow, or style. Converts corrections into Jumbo guidelines or invariants so future sessions receive the constraint.
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing. Captures new learnings, updates stale entities, and ensures documentation reflects the work performed.
| name | decompose-architecture-aggregate |
| description | Use when a project has Architecture data that needs migrating to fine-grained entities (Decisions, Invariants, Components, Dependencies). Guides the agent through reading, mapping, confirming, and executing the migration with user oversight. |
Migrate Architecture entity data to fine-grained entities with user confirmation at each step.
The Architecture entity is deprecated. Its sections map to dedicated entity types as defined in ARCHITECTURE_MIGRATION_MAPPING (src/application/context/architecture/ArchitectureDeprecationConstants.ts):
| Architecture Section | Target Entity | Command |
|---|---|---|
| patterns | Decisions | jumbo decision add |
| principles | Invariants | jumbo invariant add |
| organization | Invariants | jumbo invariant add |
| dataStores | Components | jumbo component add |
| stack | Dependencies | jumbo dependency add |
jumbo architecture view
Parse the output. If no Architecture data exists, inform the user and stop.
For each non-empty section in the Architecture view, build a mapping proposal:
--title, --context (use the pattern description), --rationale (why this pattern was chosen, if stated).--title, --description (the principle text), and --rationale if the source explains why the principle is non-negotiable.--title, --description (the organizational rule), and --rationale if the source explains why the rule is non-negotiable.--name, --type (select from: service, db, queue, ui, lib, api, worker, cache, storage), --description, --responsibility, --path (ask the user if not derivable from the data).--name, --ecosystem (e.g., npm, pip, maven, service), --package-name, --version-constraint (if known).Present all proposed mappings to the user in a single summary, grouped by target entity type. For each proposed mapping, show:
Ask the user to confirm, adjust, skip, or augment each mapping. Do not execute any commands until the user has reviewed the full set.
Execute each confirmed mapping one at a time using the appropriate jumbo command:
jumbo decision add --title "..." --context "..." [--rationale "..."] [--alternative "..."]jumbo invariant add --title "..." --description "..." [--rationale "..."]jumbo component add --name "..." --type "..." --description "..." --responsibility "..." --path "..."jumbo dependency add --name "..." --ecosystem "..." --package-name "..." [--version-constraint "..."]Report the result of each command (success or failure) before proceeding to the next.
After all confirmed mappings are processed, present a summary: