Files
portfolio-hub/.github/templates/data-model.md
T
genichin 362b008940 Squashed '.vendor/stage-pilot/' changes from 7ab085e..551777b
551777b feat: add interface contract and data model baseline support to bootstrap-baseline
f17e086 feat: add bootstrap seed file support to bootstrap-baseline skill
be85338 feat: introduce lightweight change path, change-req skill, and release feedback loop
949bb40 docs(skill): new-discovery 병렬 Discovery 및 active-cycle 처리 규칙 강화
7f96130 docs: fix draft-req skill template paths
94b1445 diff --git a/.github/skills/draft-batch-design/SKILL.md b/.github/skills/draft-batch-design/SKILL.md index 5f87d00..944e075 100644 --- a/.github/skills/draft-batch-design/SKILL.md +++ b/.github/skills/draft-batch-design/SKILL.md @@ -1,6 +1,6 @@  ---  name: draft-batch-design -description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, or recording architecture and interface decisions before implementation." +description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, recording architecture and interface decisions before implementation, or planning updates to docs/project-structure.md and docs/runtime-flows.md."  argument-hint: "예: bat-001 또는 docs/batches/bat-001_20260424_scaffold"  user-invocable: true  --- @@ -9,27 +9,43 @@ user-invocable: true
d1ce3ce 프로세스 완전 변경

git-subtree-dir: .vendor/stage-pilot
git-subtree-split: 551777bc7009ee133fbaab1267ca324f1dc3c6bb
2026-04-30 13:00:41 +00:00

88 lines
2.8 KiB
Markdown

# {{PROJECT_NAME}} Data Model
- Baseline Mode: {{BASELINE_MODE:declared|observed|mixed}}
- Baseline Seed: {{BASELINE_SEED_PATH:.stagepilot/bootstrap/baseline.yaml}}
- Status: draft | confirmed
- Owner: {{OWNER_OR_TEAM}}
- Last Updated (KST): {{UPDATED_AT_KST}}
- Source Discovery / Batch: {{SOURCE_REF}}
## Project Summary
- {{PROJECT_SUMMARY:one-sentence summary of the project}}
## Primary Domain
- {{PRIMARY_DOMAIN:short domain phrase or undecided}}
## Primary Persistence Backend
- {{PERSISTENCE_BACKEND:primary persistence backend or storage system}}
## Purpose
- This document captures the approved cross-cutting data model baseline for the project.
- It is a shared reference for REQ drafting, batch design, implementation, verification, migration planning, and handoff.
## Scope
- Covers core entities, relationships, states, persistence mappings, and shared consistency rules.
- Does not duplicate full functional acceptance criteria already owned by REQ documents.
- Does not replace ORM definitions, migration files, or generated schema artifacts.
## Model Summary
{{MODEL_SUMMARY_BULLETS:- - <entity name> :: <role in the system>}}
## Entity: `{{ENTITY_NAME_1:primary entity}}`
- Purpose: {{ENTITY_PURPOSE_1:what this entity represents}}
- Source of Truth: {{ENTITY_SOURCE_1:table, collection, file, or service}}
- Lifecycle: {{ENTITY_LIFECYCLE_1:created -> updated -> archived}}
### Key Fields
{{ENTITY_FIELDS_1:- <field name> :: <type or shape> :: <meaning>}}
### Relationships
{{ENTITY_RELATIONSHIPS_1:- <related entity> :: <relationship meaning>}}
### State Rules
{{ENTITY_STATE_RULES_1:- <state or invariant rule>}}
## Entity: `{{ENTITY_NAME_2:secondary entity}}`
- Purpose: {{ENTITY_PURPOSE_2:what this entity represents}}
- Source of Truth: {{ENTITY_SOURCE_2:table, collection, file, or service}}
- Lifecycle: {{ENTITY_LIFECYCLE_2:created -> updated -> archived}}
### Key Fields
{{ENTITY_FIELDS_2:- <field name> :: <type or shape> :: <meaning>}}
### Relationships
{{ENTITY_RELATIONSHIPS_2:- <related entity> :: <relationship meaning>}}
### State Rules
{{ENTITY_STATE_RULES_2:- <state or invariant rule>}}
## Shared Consistency Rules
{{CONSISTENCY_RULE_BULLETS:- - <uniqueness, referential, or retention rule>}}
## Persistence / Integration Notes
{{PERSISTENCE_NOTES_BULLETS:- - <mapping, indexing, migration, or synchronization note>}}
## Current Gaps / Planned Changes
{{MODEL_CURRENT_GAPS_BULLETS:- - <known model gap or planned schema change>}}
## Update Triggers
- Update this document when a core entity, key field, or relationship changes.
- Update this document when lifecycle or persistence behavior changes.
- Update this document when a batch introduces a migration, backfill, or breaking data assumption.
## Change Log
{{CHANGE_LOG_BULLETS:- - <change log entry>}}