concept-implement

Translate approved concept design specifications into Go code modules.

Updated May 3, 2026
One-click install
npx skills add https://github.com/druejaramillo/skills --skill concept-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: concept-implement
Source: https://github.com/druejaramillo/skills/tree/main/concept-design/concept-implement
Command: npx skills add https://github.com/druejaramillo/skills --skill concept-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill bridges the gap between abstract software concept designs and concrete implementation, ensuring that logical ownership, invariants, and behavioral boundaries are preserved during the coding process.

Core Features & Use Cases

  • Architecture Translation: Maps concept specs to module responsibilities, public action seams, and logical state ownership.
  • Synchronization Management: Implements composed business rules across multiple concepts while maintaining explicit consistency and retry boundaries.
  • Use Case: Use this skill when you have an approved concept spec and need to implement the corresponding Go packages, database schemas, and synchronization logic without blurring the boundaries between independent concepts.

Quick Start

Use the concept-implement skill to translate the approved Label concept spec into the existing Go codebase while preserving logical ownership.

Frequently Asked Questions about concept-implement

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

FAQPage Schema
How do I translate concept designs into Go code modules?

To translate concept designs into Go code modules, you map approved specifications to module responsibilities, public action seams, and logical state ownership. This preserves invariants and behavioral boundaries during the coding process.

What is concept-based domain modeling in software architecture?

Concept-based domain modeling is an architecture approach that maintains semantic ownership and logical independence by mapping concept specs to module responsibilities. It ensures behavioral boundaries and invariants are preserved during implementation.

How do I implement cross-concept synchronization in Go?

Implementing cross-concept synchronization in Go requires composing business rules across multiple concepts while maintaining explicit consistency and retry boundaries. This preserves logical independence between independent concepts.

How do I maintain logical independence when implementing state models?

Maintaining logical independence when implementing state models requires adherence to established dependency boundaries and explicit handling of invariants. This prevents blurring behavioral boundaries between independent concepts during implementation.

When do I need explicit consistency boundaries for domain modeling?

Explicit consistency boundaries for domain modeling are needed when implementing composed business rules across multiple concepts. They ensure logical independence is preserved and failure cases are handled without blurring concept boundaries.

Do I need an approved concept spec before implementing Go packages?

An approved concept spec is required before implementing Go packages, database schemas, and synchronization logic. The spec provides the specifications necessary to map module responsibilities and preserve logical ownership during coding.