skills.rest
LopeWale
LopeWaleCOMMUNITY
Explore all skills by this author →
Website𝕏@lopewale01GitHub

pm-document

Extract structured PM decisions from sprint reports and project artifacts.

Updated Feb 3, 2026
Search Tags:#reports#documentation#coordination#sprint#pm#audits#decision-extraction
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill pm-document
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-document
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-document
Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts sprint outputs, team reports, issue investigations, and security audits into structured PM decisions, ensuring comprehensive documentation and traceability for coordination across teams.

Core Features & Use Cases

  • Extracts architectural decisions, tech facts, enforcement lessons, issue states, and sprint records from project artifacts.
  • Generates atomic decision notes with linked references and templates for consistent reporting.
  • Supports retrieval and updating of existing decisions to prevent duplication and maintain a single source of truth for PM coordination.

Quick Start

Process the latest sprint report with /pm-document to generate structured decision notes.

Frequently Asked Questions about pm-document

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract PM decisions from sprint reports and project documentation?▼

You can extract PM decisions from sprint reports by processing project artifacts to generate atomic decision notes with linked references, ensuring traceable source attribution for architectural, tech-fact, and enforcement decisions.

What is the best way to document issue investigations and security audits for cross-team coordination?▼

Documenting issue investigations and security audits for cross-team coordination is best achieved by extracting structured issue states and sprint records into atomic decision notes, establishing a single source of truth with traceable source attribution across teams.

Can I update existing architectural decisions and prevent duplication in PM documentation?▼

Yes, you can update existing architectural decisions and prevent duplication by retrieving and updating current PM records, maintaining a single source of truth for coordination across teams without creating redundant documentation.

Does this PM documentation approach support enforcement lessons and tech facts from team reports?▼

Yes, this PM documentation approach supports extracting enforcement lessons, tech facts, and issue states from team reports, converting sprint outputs and security audits into structured decisions with consistent reporting templates.

What are the limitations of automating decision extraction from project artifacts?▼

Automating decision extraction from project artifacts requires comprehensive documentation inputs like sprint outputs or security audits to function properly, limiting effectiveness if source artifacts lack sufficient detail or structured decision context.

Related Skills

Explore More Product & Management Skills→
CHNISamCHNISam

linear

Create, update, and retrieve Linear issues with priorities and statuses.

Community
Intermediate
Prat011Prat011
1.5k

notion-knowledge-capture

Extract key concepts and decisions from conversations into structured Notion pages.

Community
Advanced
LopeWaleLopeWale

pm-seed

Extract decisions, architecture notes, issues, and sprint data from project documentation.

Community
Advanced
darelabs-techdarelabs-tech

dare-patterns

Mine brownfield software patterns via AST analysis to generate architectural documentation and JSON facts.

Official
Intermediate