Project Docs v1.1 — Professional Project Documentation Aligned with PMBOK, ISO 31000 & EVM Standards

Turn a 90-minute weekly status report process into a 10-minute workflow with polished, stakeholder-ready project documents grounded in professional PM frameworks.

Installation

1. Download the pf-project-docs.plugin file
2. Open Claude Desktop and navigate to Settings > Plugins
3. Click Install Plugin and select the downloaded .plugin file
4. The plugin will be installed and available immediately

Note: All data stays local on your machine. No external API calls or cloud storage required.

Why This Exists

SMB teams pay $1,080–3,600/yr for Monday.com, Asana, or Wrike — often just for the reporting features. But generating polished project documents (status reports, risk registers, lessons learned) is still a tedious manual process even WITH those tools. Project Docs automates the document creation workflow entirely: feed in a CSV or text notes, get professional DOCX and XLSX output aligned with PMBOK 7th Edition, ISO 31000:2018, and ANSI/EIA-748 standards.

Quick Start

1. Install the plugin in Cowork
2. Run /project-docs:project-docs-setup to create your workspace and check dependencies
3. Place your project data in the inputs/ folder (CSV or text notes)
4. Run /project-docs:project-docs-status-report to generate your first status report
5. Find your document in pf-project-docs/outputs/

Commands

Command	Description
/project-docs:project-docs-setup	Initialize workspace with PM methodology selection, check dependencies
/project-docs:project-docs-status-report	Generate status report (DOCX) with EVM metrics per ANSI/EIA-748
/project-docs:project-docs-risk-register	Create risk register (XLSX) aligned with ISO 31000:2018
/project-docs:project-docs-lessons-learned	Generate lessons learned (DOCX) with PMI knowledge taxonomy
/project-docs:project-docs-milestones	Generate milestone tracker (XLSX) with CPM analysis
/project-docs:project-docs-stakeholder-register	Generate stakeholder register (XLSX) with Mendelow grid
/project-docs:project-docs-full-suite	Generate all five documents in one run
/project-docs:project-docs-status	Show workspace status and pipeline state
/project-docs:project-docs-setup	Re-configure workspace (methodology, industry, EVM settings)

How It Works

Each document type is an independent skill — you can run them individually or together via full-suite. Input data flows like this: your CSV/text files in inbound/ are parsed and validated against professional PM framework standards, then python-docx or openpyxl generates professional documents saved to your persistent outputs/ folder. Each skill handles its own input parsing, validation, and error logging independently.

What It's an Alternative To

SaaS Tool	Annual Cost (5 users)	Key Overlap
Monday.com	$1,080–2,400/yr	Status dashboards, project reporting
Asana	$1,320–3,600/yr	Project status updates, milestone tracking
Wrike	$1,188–2,988/yr	Custom reports, Gantt-based milestone views

Key Differentiators

• Included with your subscription — an alternative to $1,080–3,600/yr in project management document creation fees
• Framework-aligned — outputs reference PMBOK 7th Ed, ISO 31000:2018, ANSI/EIA-748, and PRINCE2
• Data stays local — project data, risks, and lessons learned is processed within the Cowork environment
• Better documents — generates polished DOCX/XLSX output vs. raw board exports from SaaS tools
• No feature bloat — focused on project documentation, not task tracking or team chat
• Customizable templates — edit Word/Excel templates to match your company branding

Feature Comparison

Feature	Project Docs v1.1	Monday.com	Asana
Status reports (DOCX) with EVM	✅ Full + ANSI/EIA-748	⚠️ PDF export only	⚠️ PDF export only
Risk register (XLSX) ISO 31000	✅ Full + response strategies	⚠️ Board view only	❌ None
Lessons learned (DOCX) PMI taxonomy	✅ Full + retro formats	❌ None	❌ None
Milestone tracking (XLSX) with CPM	✅ Full + critical path	✅ Timeline view	✅ Timeline view
Stakeholder register (XLSX)	✅ Full + Mendelow grid	❌ None	❌ None
PM framework alignment	✅ PMBOK/ISO/EVM	❌ None	❌ None
Custom templates	✅ Full	❌ None	❌ None
Data privacy	Local processing	❌ Cloud-hosted	❌ Cloud-hosted
Real-time task tracking	❌ None	✅ Full	✅ Full
Team collaboration	❌ Single-user	✅ Full	✅ Full
Gantt charts	❌ None	✅ Full	✅ Full

Estimated Cost per Use

Disclaimer: Token estimates are approximate and based on typical usage patterns measured from skill prompt sizes. Actual costs vary with input data size, conversation length, and complexity. Estimates use Claude Sonnet 4.6 pricing ($3/1M input, $15/1M output). Cowork and Claude Desktop subscription users (Pro/Max/Team) are not charged per-token — these estimates apply only to direct Anthropic API usage. Running stages individually in fresh sessions uses fewer input tokens than running the full pipeline sequentially, because pipeline mode accumulates conversation history across stages.

Per skill (run individually in a fresh session):

Stage	Skill Prompt	User Input	Total Input	Output	Est. Cost
project-docs-lessons-learned	~4.2K	~800	~7.9K	~4.2K	~$0.09
project-docs-milestones	~5.0K	~800	~8.7K	~5.0K	~$0.10
project-docs-risk-register	~6.7K	~800	~10.4K	~6.0K	~$0.12
project-docs-stakeholder-register	~5.9K	~800	~9.5K	~5.9K	~$0.12
Standalone total			~36.4K	~21.2K	~$0.43

Full pipeline (all stages in one session — context accumulates):

Stage	Base Input	+ History	Total Input	Output	Est. Cost
project-docs-lessons-learned	~8.7K	0	~8.7K	~4.2K	~$0.09
project-docs-milestones	~9.5K	~5.0K	~14.5K	~5.0K	~$0.12
project-docs-risk-register	~11.1K	~10.8K	~22.0K	~6.0K	~$0.16
project-docs-stakeholder-register	~10.4K	~17.6K	~28.0K	~5.9K	~$0.17
Pipeline total			~73.1K	~21.2K	~$0.54

Running the full pipeline once typically costs $0.38–$0.70 in API tokens (Claude Sonnet 4.6).

AI-Powered Features

• EVM Performance Analysis: Calculates SPI, CPI, EAC, ETC, VAC per ANSI/EIA-748 with traffic-light thresholds
• ISO 31000 Risk Framework: Risk identification, analysis, evaluation, and treatment aligned with ISO 31000:2018
• PMBOK-Aligned Status Reports: PRINCE2 Highlight Report format with tolerance-based RAG definitions
• Critical Path Analysis: Identifies zero-float activities and schedule performance per PMI Practice Standard
• Stakeholder Engagement Assessment: Power/Interest Grid (Mendelow, 1991) and PMBOK Ch.13 engagement matrix
• Knowledge Management Taxonomy: Lessons categorized per PMI Practice Standard for Project Knowledge Management
• Multi-Format Retrospectives: Starfish, 4Ls, Start-Stop-Continue, and standard retrospective analysis
• Industry-Specific Risk Categories: Pre-configured for IT, construction, healthcare, and financial services

Known Limitations & Workarounds

This is a Claude Cowork plugin, not a traditional SaaS application. It has architectural constraints you should know about before adopting it.

Limitation	Impact	Workaround
No real-time task tracking	Cannot track tasks, assignments, or Kanban boards	Keep your task tracker (Trello/Notion) and export CSV for reporting
No team collaboration	Single-user operation; can't co-edit risk registers	PM generates documents and shares via email/SharePoint
No persistent scheduling	Can't auto-generate weekly reports on a schedule	Pair with Cowork scheduled tasks, or run Monday mornings
Input data dependency	Report quality depends on input completeness	Setup generates sample CSV templates with clear field descriptions
No Gantt chart rendering	Can't generate visual timelines	XLSX date columns work with Excel's built-in chart tools

Context & Performance Guide

Session management: Claude's context window (200K tokens) is shared across the entire session. For running the full suite (5 documents), consider starting a fresh session for best quality.

Data volume guidance: Tested with up to 200 milestones/risks per document. Each skill typically uses 5-15K tokens depending on data volume. For datasets exceeding 200 entries, the command files use subagent isolation to maintain output quality.

Tips for best results:

1. Provide input data as CSV files rather than pasting into chat — file reading is more context-efficient
2. Keep your messages concise during pipeline runs — every message stays in the context window
3. Use consistent date formats (YYYY-MM-DD works best) across all input files
4. For the highest quality output, run each document in a separate session

Degradation signals: If responses become shorter, less detailed, or skip sections that previously worked well, start a new session and re-run the current stage.

Requirements

• Claude Desktop with Cowork mode
• Python 3 (auto-checked during setup)
• python-docx library (auto-installed during setup)
• openpyxl library (auto-installed during setup)

Important Disclaimers

• AI-Generated Content: This plugin uses AI (LLM) technology which can produce inaccurate or incomplete outputs. All content should be treated as a starting point and reviewed for accuracy before use.
• Not Professional Advice: Outputs do not constitute legal, financial, tax, medical, or other professional advice. Consult qualified professionals before making decisions based on generated content.
• No Compliance Guarantee: References to industry standards (PMBOK, ISO 31000, ANSI/EIA-748, PRINCE2) are for informational purposes only. This plugin does not guarantee compliance with any standard or certification. Users are responsible for verifying all outputs meet their specific requirements.
• No Endorsement or Affiliation: Mention of PMI, ISO, AXELOS, or other standards bodies does not imply endorsement, partnership, or certification by those organizations.