Run any Skill in Manus with one click

cap4k-tactical-modeling

Stars3

Forks0

UpdatedJune 4, 2026 at 20:03

Use when a coherent cap4k business brief needs tactical DDD decisions mapped to cap4k carriers, generator input expectations, rollback notes, and the next technical design phase.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

LDmoxeii

LDmoxeii/cap4k

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	cap4k-tactical-modeling
description	Use when a coherent cap4k business brief needs tactical DDD decisions mapped to cap4k carriers, generator input expectations, rollback notes, and the next technical design phase.

Cap4k Tactical Modeling

Map business language to cap4k tactical carriers.

Always Read

../shared/references/tactical-affordance-map.md
../shared/workflows/forced-rollback.md
workflows/map-tactical-carriers.md

Rules

Start from a business brief, not table shape or generator convenience.
Every generic DDD concept must map to a cap4k carrier or stay an open decision.
Record rollback notes when a business signal has no clear carrier.
Route to cap4k-technical-design only after the carrier table is coherent.

More from this repository

same repository

cap4k-generator-inputs

LDmoxeii/cap4k

Use when projecting an approved cap4k technical design into generator inputs such as DB/schema, design JSON, manifests, Gradle extension settings, addons/options, or template override decisions.

2026-07-183

cap4k-authoring

LDmoxeii/cap4k

Route cap4k business-authoring work through the self-contained cap4k skill system. Use when the user asks to discover a business slice, model DDD boundaries, write cap4k technical design, author generator inputs, review plan or generated output, implement handwritten business logic, design service integration, or verify cap4k work.

2026-06-063

cap4k-service-integration

LDmoxeii/cap4k

Use for cap4k business service interaction design and implementation: Open Host Service entries, Published Language, external capability clients, external fact entries, inbound/outbound integration events, callbacks, message listeners, and command/query routing across service boundaries.

2026-06-043

cap4k-handwritten-implementation

LDmoxeii/cap4k

Use when implementing cap4k handwritten business logic inside approved generated skeletons after human generated-output review: command handlers, query handlers, subscribers, jobs, controllers, factories, specifications, domain services, Repository access, Mediator routing, and UoW persistence.

2026-06-043

cap4k-verification-audit

LDmoxeii/cap4k

Use for cap4k verification and audit claims: static review, focused local evidence, full evidence, generated-versus-handwritten ownership checks, skipped-check disclosure, rollback targeting, and final evidence summaries.

2026-06-043

cap4k-generation-review

LDmoxeii/cap4k

Use to review cap4k plan evidence, generated output ownership, conflict policies, template IDs, addon artifacts, generation drift, and the stop point before handwritten implementation.

2026-06-043

Run any Skill with one click