Project Management

Project Management

74 projects tracked across workstation deployments, infrastructure, software, and migrations. STD-001 governs project structure. The ThinkPad P16g Deploy serves as the reference implementation.

STD-001 Compliance Audit

Category Count Detail

Fully compliant

5

4+ files each (metadata, summary, appendix-issues, appendix-todos minimum)

Partially compliant

61

Have metadata and summary but missing required appendices

Non-compliant

6

Pages-only — content lives in pages/ with no partials

Orphaned partials

3

Partials exist with no corresponding container page

Reference Implementation

ThinkPad P16g Deploy: 27 files across 13 phases, 8 appendices, plus required metadata.

partials/projects/thinkpad-p16g-deploy/
├── metadata.adoc
├── summary.adoc
├── assessment.adoc
├── phase-00-pre-work.adoc
├── phase-01-foundation.adoc
├── phase-02-desktop.adoc
├── phase-03-networking.adoc
├── phase-04-development.adoc
├── phase-05-security.adoc
├── phase-06-containers.adoc
├── phase-07-virtualization.adoc
├── phase-08-secrets.adoc
├── phase-09-certificates.adoc
├── phase-10-monitoring.adoc
├── phase-11-backup.adoc
├── phase-12-validation.adoc
├── phase-13-documentation.adoc
├── appendix-issues.adoc
├── appendix-todos.adoc
├── appendix-scope-creep.adoc
├── appendix-deviations.adoc
├── appendix-commands-learned.adoc
├── appendix-hardware.adoc
├── appendix-stow-audit.adoc
└── appendix-field-notes.adoc

Project Archetypes

Phased (deployments, migrations):

  • Numbered sequential phases — order matters

  • Phases never renumbered after completion — scope grows by appending

  • Split phases permitted: phase-08-secrets.adoc, phase-08-eaptls.adoc

  • Use when: work has a clear start-to-finish sequence

Feature-based (software, configs):

  • Domain-specific names, no numbering

  • Features are independently navigable

  • Use when: components are parallel, not sequential

  • Reference: tmux-quantum (architecture, keybindings, themes, deployment, decision-log)

Required Files

Every project, regardless of archetype, must contain:

File Required Purpose

metadata.adoc

Always

PRJ ID, author, dates, status, category, priority

summary.adoc

Always

Status table with phase/feature progress

appendix-issues.adoc

Always

Issues encountered during the project

appendix-todos.adoc

Always

Outstanding work items and post-completion tasks

Container Page Pattern

Every page is a 6-line shell with exactly one include:: directive. No content lives in pages — partials hold all content.

= Page Title
:description: One-line description for SEO
:navtitle: Short Nav Title
:icons: font

include::partial$projects/<slug>/<partial>.adoc[]

This pattern ensures single source of truth. Content changes happen in partials; page structure never changes.

Remediation Roadmap

Phase Scope Work

Phase 1

61 projects

Add appendix-issues.adoc and appendix-todos.adoc to partially compliant projects

Phase 2

6 projects

Convert pages-only projects to partial-based structure with container pages

Phase 3

25 files

Convert flat PRJ-*.adoc files to full STD-001 project directories

/project Skill

The /project skill automates project management operations:

Command Purpose

create

Scaffold new project with all required files and nav entry

audit

Check STD-001 compliance across all projects

add-phase

Add numbered phase to phased project

add-feature

Add feature file to feature-based project

status

Show project status summary (phase progress, open issues)

list

List all projects with compliance status

tree

Display project file tree