v1
2Layer 2 · Reference Approach

Quickstart with Claude Code.

Skip the manual steps. Copy one prompt, paste it into Claude Code, and it scaffolds the pipeline, converts your documents, and wires the gate, asking you for the specifics as it goes.

Prefer to do it by hand? See the manual quickstart →

The prompt.

set up the whole pipelinepaste into Claude Code
Set up "PMO as Code" in this repository using docassert
(pip install docassert · https://github.com/c4g-john/docassert).

1. Add docassert and its GitHub Actions workflows: validate + consistency on
   every pull request plus the status-pages dashboard, using
   c4g-john/docassert-action@v1 (copy the workflows from
   github.com/c4g-john/pmo-as-code-template).
2. Create a project anchor at documents/PRJ-001-<CODE>/project.md with a
   unique id, a short CODE, a sponsor, and a profile (start with lean-startup).
3. Turn my existing project docs into PMO-as-Code documents using the standard
   templates: charter, business requirements, product requirements, test cases.
   Flag anything the source doesn't cover as a TODO; never invent facts.
4. Run docassert validate and docassert consistency, and fix whatever blocks.
5. Show me docassert status --project PRJ-001-<CODE>, then tell me exactly what
   to click to turn on branch protection and GitHub Pages.

Start by asking me for the project name, sponsor, and any existing documents.

The button copies the prompt and opens claude.ai/code, where you paste and send. Or run claude in your terminal and paste.

What you'll need.

Claude Code
The terminal claude CLI, the desktop app, or the web app at claude.ai/code. Install from claude.com/claude-code.
A GitHub repo
New or existing. Claude adds the pipeline and workflows in a branch and opens a pull request, so nothing lands on main until you approve it.

What Claude will do.

It follows the same path as the manual quickstart, drives it for you, and stops to ask whenever a decision is yours.

01
Add docassert + the CI workflows
the tool, plus audit / consistency / status-pages
02
Anchor your project
project.md with a unique id, code, and a profile
03
Convert your documents
into the standard templates, with gaps marked as TODOs
04
Validate and check consistency
and fix whatever blocks a merge
05
Derive the status page
RAG, coverage, and the required-document set
06
Explain the repo setup
branch protection and Pages, the one-time manual settings

More prompts.

Smaller, targeted asks once you're set up.

convert one Word documentpaste into Claude Code
Convert this Word document into a PMO-as-Code charter using docassert
(pip install docassert · github.com/c4g-john/docassert). Extract the text, map it
to the charter template, and flag anything the source is missing as a TODO
rather than inventing it. Then run docassert validate and show me what fails.
add a project to an existing setuppaste into Claude Code
We already use docassert. Add a new project: create
documents/PRJ-00N-<CODE>/project.md (pick the next free number and a short
CODE), set a profile, regenerate projects.yaml, and scaffold its charter.
Then run docassert consistency and docassert status --project for the new project.
What's next

See the steps Claude runs in the manual quickstart, or browse the document kinds and guides.