Concept PRD
Focus: how can a confirmed model be persisted without losing purpose, behavior, or acceptance
traceability? Run only on explicit $concept-prd invocation. Input includes concepts,
synchronizations, dependencies, exclusions, and open decisions. Route model gaps to concept-design
and code realization to concept-implementation.
A confirmed model is the authorized set of purposes, behaviors, and choices. Its authoritative
specifications are the single persisted home: CONCEPT for concepts, SYNCS for coordination, and the
overall PRD for global relations. Preserve both design arguments—contract → OP → concept purpose,
and selection/sync → application scenario → application purpose—and their assumptions. Acceptance
scenarios derive from OPs or behavioral contracts and never invent requirements.
Transcribe
Verify input — Read the confirmed model, requirement sources, and existing documents. Inspect
code only for module locations and indexing facts. Never let implementation differences silently
rewrite the model.
Choose locations — Use the following layout. Stage centrally only until modules exist.
docs/prd/README.md
<module>/CONCEPT.md or docs/prd/concepts/<name>.md
<syncs>/SYNCS.md or docs/prd/SYNCS.md
Write the overall PRD — Preserve application purpose, end-to-end scenarios and their
concept/sync basis, misfits, concept index with purpose and links, synchronization graph, product
dependencies and subsets, exclusions, and open decisions. Put cross-concept assumptions and
arguments here.
Write specifications and acceptance — Read references/spec-format.md and
references/templates.md. Preserve the four CONCEPT sections, concept-local assumptions, and
purpose argument; put application context in notes. Transcribe app/include/sync into one SYNCS
file grouped by entry point or rule responsibility with // flow:. Derive acceptance separately
from concept OPs, application scenarios, and behavioral contracts, each with provenance. Mark
missing application goals as open rather than constructing them from concept purposes.
Update consistently — Make minimal edits to existing documents, refresh indexes and derived
diagrams, and preserve human-maintained content. Leave implementation-time migration and sync
package splitting to concept-implementation.
Completion requires one authoritative location per model element; no lost definitions, relations,
assumptions, exclusions, or open decisions; independent CONCEPT sections; application instantiation
in SYNCS rather than legacy interactions/dependencies sections; acceptance linked to OP, application
scenario, or contract evidence; real sync declarations for every parameter, binding, and output;
preserved reachable failure behavior and empty-query semantics; and valid global links.
For the first transcription read references/example-reserving.md; for specification sources read
references/sources.md.
1---2name: concept-prd-23description:4 Transcribes a confirmed concept model into traceable PRD and colocated specification files only5 when the user explicitly invokes $concept-prd. Use to preserve purposes, behavior,6 synchronizations, assumptions, exclusions, open decisions, and acceptance provenance without7 redesigning the model.8metadata:9 source: https://skillmd.com/skills/ontology-of-everything/concept-prd-210 language: en11 translation_of: concept-prd-cn12 openclaw:13 homepage: https://github.com/ontology-of-everything/concept-skills/tree/main/skills/en/concept-prd14---1516# Concept PRD1718Focus: how can a confirmed model be persisted without losing purpose, behavior, or acceptance19traceability? Run only on explicit `$concept-prd` invocation. Input includes concepts,20synchronizations, dependencies, exclusions, and open decisions. Route model gaps to `concept-design`21and code realization to `concept-implementation`.2223A confirmed model is the authorized set of purposes, behaviors, and choices. Its authoritative24specifications are the single persisted home: CONCEPT for concepts, SYNCS for coordination, and the25overall PRD for global relations. Preserve both design arguments—contract → OP → concept purpose,26and selection/sync → application scenario → application purpose—and their assumptions. Acceptance27scenarios derive from OPs or behavioral contracts and never invent requirements.2829## Transcribe30311. **Verify input** — Read the confirmed model, requirement sources, and existing documents. Inspect32 code only for module locations and indexing facts. Never let implementation differences silently33 rewrite the model.342. **Choose locations** — Use the following layout. Stage centrally only until modules exist.3536 ```text37 docs/prd/README.md38 <module>/CONCEPT.md or docs/prd/concepts/<name>.md39 <syncs>/SYNCS.md or docs/prd/SYNCS.md40 ```41423. **Write the overall PRD** — Preserve application purpose, end-to-end scenarios and their43 concept/sync basis, misfits, concept index with purpose and links, synchronization graph, product44 dependencies and subsets, exclusions, and open decisions. Put cross-concept assumptions and45 arguments here.464. **Write specifications and acceptance** — Read `references/spec-format.md` and47 `references/templates.md`. Preserve the four CONCEPT sections, concept-local assumptions, and48 purpose argument; put application context in notes. Transcribe app/include/sync into one SYNCS49 file grouped by entry point or rule responsibility with `// flow:`. Derive acceptance separately50 from concept OPs, application scenarios, and behavioral contracts, each with provenance. Mark51 missing application goals as open rather than constructing them from concept purposes.525. **Update consistently** — Make minimal edits to existing documents, refresh indexes and derived53 diagrams, and preserve human-maintained content. Leave implementation-time migration and sync54 package splitting to `concept-implementation`.5556Completion requires one authoritative location per model element; no lost definitions, relations,57assumptions, exclusions, or open decisions; independent CONCEPT sections; application instantiation58in SYNCS rather than legacy interactions/dependencies sections; acceptance linked to OP, application59scenario, or contract evidence; real sync declarations for every parameter, binding, and output;60preserved reachable failure behavior and empty-query semantics; and valid global links.6162For the first transcription read `references/example-reserving.md`; for specification sources read63`references/sources.md`.