How to Kick Off a New Project With the Documentation Methodology

William Warne

Software Engineer | Fractional CTO | Founder

Introduction

New projects don't have to start with a blank slate and "we'll document later." You can have methodology, standards, and a clear sequence of steps from day one. This post shows how to kick off a new project using the Documentation Management Pack—install, compile, then work in order so documentation issues never pile up.

What You Get After Install

Once you install the pack (from scratch flavour), you have:

  • Standard directory structure — docs/01-concept-of-operations/ through docs/10-operational-procedures/ and docs/local/. Each directory has a draft document with a Methodology section that tells you how to work through that document.
  • A clear sequence — Work in order: 01 Concept of Operations → 02 Stakeholder Requirements → 03 System Requirements → 04 Architecture & Integration → 05 Component Specifications (one per bounded context), then 06–10 as needed.
  • AI that knows the methodology — After you run ctx compile, Cursor and Claude have the rules and skills. When you ask "what should I document next?", the AI suggests the next document and guides you through it.

Step 1: Download and Install the Pack

Download the pack (ZIP or via the context CLI). Install with the from scratch flavour so you get docs/01–10 and draft templates. Copy the pack content into your project (or use the pack installer). Ensure docs/01-concept-of-operations/ through docs/10-operational-procedures/ and docs/local/ exist with draft templates in each.

Step 2: Run ctx compile

From the repo root, run:

ctx compile --pack pack-01-documentation-management

That builds AI context—Cursor rules, skills, CLAUDE.md—so your AI has the methodology. From then on, when you ask the AI to create or update documentation, it follows your standards and suggests the next document in order.

Step 3: Work in Methodology Order

Start with 01 Concept of Operations, then 02 Stakeholder Requirements, then 03, 04, 05 (one component spec per bounded context), then 06–10 as needed. For each document, use the Methodology section in the draft—it tells you how to fill it out and what "done" looks like. Apply document structure, traceability, and naming conventions from the start. No "we'll clean up later."

Step 4: Transition to Maintain

Once your initial 01–10 set is in place, treat the repo as "maintain and improve": when product or requirements change, update the right doc (01, 02, 03, 05, or 08) and keep traceability. The pack's Guide C (maintain) covers when to update which doc and how to keep standards from drifting.

Conclusion

Kick off new projects with structure from day one. Install the pack, run compile, work in order. Your AI suggests the next document and follows your standards—so you never start from zero and never pile up doc debt.

Get the pack. Try the CLI.