Design-Table

Writes <docs>/table.md against the host's table.template.md, then renders <output>/table.docx. Conventions: design-docs.md.

Precondition: .claude/harness-tier/scripts/design_doc_check.py must exist. If it doesn't, tell the user to run /flow-init and stop.

Interaction. Wherever this skill asks the user something, use the host's blocking question tool already in your tool list, matched by capability rather than by a host-specific name; if it is listed but not loaded, load it first with the host's tool-discovery primitive; only when no such tool is listed, or a question call errors, offer numbered options in chat and end your turn to wait for the reply — never answer the question yourself or skip it.

1. Resolve paths and dependencies

python3 .claude/harness-tier/scripts/design_doc_check.py --paths
python3 .claude/harness-tier/scripts/design_doc_render.py --check-deps

When the second prints missing: ..., ask the user (structured choice) whether to install them, showing the command. Yes → run python3 -m pip install python-docx markdown-it-py and continue. No → stop; the check steps below still run without them if the user asks.

2. Check the templates

python3 .claude/harness-tier/scripts/design_doc_check.py --templates

Any violation → relay the list and stop. A template is the consumer's; do not edit it.

3. Take the code inventory

List every table the schema creates: migrations, DDL files, ORM table names. Run the listing as one command and keep it: it goes into the inventory section verbatim.

4. Write the document

Read docs/srs/, docs/sds/, erd.md and the inventory's sources. Write <docs>/table.md in the template's shape: every template heading in order, every table with the template's header, one TBL-NNN block per table, the traceability table, and the inventory. The entity column names the ENT-NNN from erd.md it realizes; a foreign key names the target TBL-NNN in the FK column. Write /design-erd first when erd.md is absent — the check skips the entity cross-check until then and says so. When the file exists, update it: keep every id, number new tables after the highest, and append one revisions row. Get wiki_id from:

python3 .claude/harness-tier/scripts/design_doc_check.py --wiki-id table

5. Check the document

python3 .claude/harness-tier/scripts/design_doc_check.py --doc table

Fix what it names and run it again, at most three rounds. Relay every violation still standing and every note: line; do not render over a violation without the user's go-ahead: ask the user (structured choice).

6. Render

python3 .claude/harness-tier/scripts/design_doc_render.py table

When flow-config.wiki is enabled, rebuild the graph so the new node is in it, and tell the user to stage graph.yaml with the document:

python3 .claude/harness-tier/scripts/wiki_graph.py --build

7. Report

The .docx path, the violation count, and every warning: line (a diagram left as code).