Dzcto init

DZ CTO Init

Set up the small Day Zero CTO surface for CEO reports only. Do not run or offer Tech Stack, risk review, snapshot, learning, decision review, or any other Day Zero CTO workflow.

Workflow

1. Resolve the artifact/report location. If the user has not given one, ask where reports should live. Prefer a durable folder outside the code repo. The helper creates an index.html, reports/ceo-updates/, and .dzcto/config.json in that location. On refresh, the helper also re-renders existing structured CEO report HTML from sibling JSON so older reports pick up the current report format without changing report data.
2. Resolve the company, CTO, or project profile name. If the user does not provide one, derive a short slug from the company/project, such as getmusic. This profile is how one global install supports multiple repos or CTO contexts.
3. Capture a one-sentence company context summary for the index page and report prompts. Ask for this during init; do not tell the user to add extra source files.
4. Ask what weekly reporting window they want. Do not silently choose Monday-Sunday. Offer since_last_report alongside concrete schedules such as Fri-Thu, Mon-Sun, previous completed week ending Thursday, or rolling last 7 days. Describe since_last_report as gapless-by-construction: each report starts the day after the previous report's window.end and runs through the run date.
5. Convert that answer into helper flags:
   • Fri-Thu means --weekly-range "previous_completed_week" --weekly-start-day "Friday" --weekly-end-day "Thursday".
   • Mon-Sun means --weekly-range "previous_completed_week" --weekly-start-day "Monday" --weekly-end-day "Sunday".
   • rolling last 7 days means --weekly-range "last_7_days" --weekly-lookback-days 7.
   • since_last_report means --weekly-range "since_last_report"; it is gapless-by-construction because each report starts the day after the previous report's window.end and runs through the run date.
6. Resolve the CEO report tone. Offer a short default such as direct, concise, business-facing, calm about risk, explicit about asks. Capture any user-specific language preference.
7. Optionally capture read-only code repo paths if the user wants report evidence from Git history or code. Treat these as evidence sources only.
8. Run the helper:

dzcto init \
  --artifacts-dir "<artifact/report folder>" \
  --profile "<profile-name>" \
  --company-name "<company name>" \
  --company-description "<one-sentence company context>" \
  --weekly-range "previous_completed_week" \
  --weekly-start-day "Monday" \
  --weekly-end-day "Sunday" \
  --ceo-report-tone "<tone guidance>"

If dzcto is not on PATH, run the plugin helper from the repo:

python3 scripts/dzcto.py init \
  --artifacts-dir "<artifact/report folder>" \
  --profile "<profile-name>" \
  --company-name "<company name>" \
  --company-description "<one-sentence company context>" \
  --weekly-range "previous_completed_week" \
  --weekly-start-day "Monday" \
  --weekly-end-day "Sunday" \
  --ceo-report-tone "<tone guidance>"

Add repeatable --repo "<path>" flags when read-only code repos should be saved as evidence sources.

The helper also saves these preferences to ~/.dzcto/config.json under profiles.<profile-name>, including the artifact directory, company context, weekly defaults, tone, and optional repos. It also updates defaultProfile unless --no-switch-default is used, so /dzcto-ceo-report-weekly and /dzcto-ceo-report can work from other repos later.

For per-flag detail, open settings.html in the artifact folder; it shows each report-shaping dzcto init flag alongside the profile's current value.

When dzcto init runs against an existing artifact folder, it refreshes index.html and re-renders any existing structured reports under reports/ceo-updates/ that have sibling .json files. Body-only legacy HTML without JSON is left unchanged.

On a workspace that has no CEO report yet, the helper also writes one sample report at reports/ceo-updates/sample-ceo-report.html so the user can open real generated output immediately and confirm the install end to end. The sample is labelled as an example in the page itself and is excluded from report counts, the weekly streak, prior-report comparison, and the since-last-report window, so it can never be read or counted as real repo evidence. It is not written once a real report exists, and --no-sample-report skips it.

Result

Confirm only the created index path, the sample report path when one was generated, the profile name, the global preferences path, the stored weekly range defaults, the stored tone guidance, and the next command to run:

• /dzcto-ceo-report-weekly for the default weekly report.
• /dzcto-ceo-report for a custom date range.

Keep the response short and practical. Do not ask whether to run any other setup/report workflow.