Skip to content

Add a Workflows section to the Claude guide (work in progress) - #194

Open
dmartinezIPA wants to merge 2 commits into
release/colombia-claude-bootstrappingfrom
feature/claude-workflows
Open

Add a Workflows section to the Claude guide (work in progress)#194
dmartinezIPA wants to merge 2 commits into
release/colombia-claude-bootstrappingfrom
feature/claude-workflows

Conversation

@dmartinezIPA

Copy link
Copy Markdown
Contributor

Pull Request Summary 🚀

Work in progress. This PR opens a new Workflows section for the Claude guide with the first workflow. More workflows are on the way (next up: a reproducible-pipeline workflow, then package-for-replication), so it stays a draft until the initial set lands.

What does this PR do? 📝

Adds a Workflows subsection under Software Guides → Claude AI:

  • software/claude/workflows/index.qmd — a link-hub landing for the section.
  • software/claude/workflows/understand-inherited-code.qmd — the first workflow, Revive and understand inherited code.
  • _quarto.yml — wires the subsection into the Claude AI sidebar.

Why is this change needed? 🤔

The existing Claude pages orient readers and show where Claude Code helps. Workflows go a level deeper: concrete, repeatable processes for the tasks where Claude does something a reference page cannot — reading, running, and reasoning about a real project. Each workflow is written to be adopted and adapted, not just read.

How was this implemented? 🛠️

  • The landing frames the section (you own the spec; the value is in the loop; nothing lands on the first try) and links to each workflow as a card.
  • The first workflow: give Claude the code and its context (with a safe, de-identified or synthetic data stand-in — never raw participant data), iterate the closed loop until it runs, and report a change log of what it altered. A base tier needs no version control; an advanced tier commits the original and has Claude produce an Explain-Diff-style interactive HTML walkthrough with a quiz (crediting Geoffrey Litt's prompt).
  • Public-audience-first voice, with IPA-specific detail scoped to "At IPA" callouts. Drafted and checked with the repo's knowledge-hub-generator skill.

Stacked on release/colombia-claude-bootstrapping (this PR targets that branch, not main) so PR #180 stays a light, independently-approvable unit.

How to test or reproduce? 🧪

just fmt-md software/claude/workflows/index.qmd
just fmt-md software/claude/workflows/understand-inherited-code.qmd
just vale-file software/claude/workflows/index.qmd
just vale-file software/claude/workflows/understand-inherited-code.qmd
just preview-docs   # browse Software Guides → Claude AI → Workflows

Both pages report 0 Vale errors and render cleanly.

Screenshots (if applicable) 📷

N/A — text pages.

Checklist ✅

  • I have run and tested my changes locally
  • I have limited this PR to less than 1000 lines of code change (if not, explain why)
  • I have run linting and formatting on any code changes (if applicable)
  • I have updated the documentation (README, etc.) accordingly — this PR is documentation; navigation updated in _quarto.yml
  • I have reviewed and resolved any merge conflicts
  • I have reviewed and resolved any Vale errors

🤖 Generated with Claude Code

dmartinezIPA and others added 2 commits August 3, 2026 08:00
Add a Workflows subsection under Claude AI: a link-hub landing plus the
first workflow, "Revive and understand inherited code" — give Claude the
code and its context, iterate until it runs, and report what it changed;
the advanced git tier produces an Explain-Diff-style walkthrough (credit
Geoffrey Litt). Wired into the Claude sidebar in _quarto.yml.

Authorship: Daniel Martinez; contributors Juan Felipe Garcia Rodriguez and
Diego Quintero Mogollon. Verified against the knowledge-hub-generator QC
checklist: fmt-md, vale (0 errors), quarto render, and house style.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Second Workflows page: Claude as a multi-language, multi-platform agent
that lays a project's foundations, wires the just orchestration, and drives
the uv -> Stata/R -> Python -> Quarto chain to a rendered deliverable. Adds a
"what the stack buys you" rationale, a safe-data rule, and a starter prompt;
cites the public ipa-stata-template and ipa-python-template. Added as a card
on the Workflows landing and wired into _quarto.yml.

Authorship: Daniel Martinez; contributors Juan Felipe Garcia Rodriguez and
Diego Quintero Mogollon. Verified against the knowledge-hub-generator
checklist plus an independent editorial review (Diataxis fit, no duplication,
public-first framing, voice).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@kellymontano
kellymontano marked this pull request as ready for review August 12, 2026 20:27
@kellymontano
kellymontano requested a review from a team as a code owner August 12, 2026 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant