Extract decisions, architecture notes, issues, and sprint data from project documentation.
npx skills add https://github.com/LopeWale/amplLABS --skill pm-seed
Please help me install this Agent Skill. Skill: pm-seed Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-seed Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-seed
Populates the PM knowledge system by importing and organizing existing project documentation, turning scattered notes into a searchable vault.
Run the /pm-seed command to bootstrap the PM vault from the project's existing documentation sources.
High-intent search queries and answers about installing and using this skill.
To extract decisions and architecture notes from existing project documentation, use a PM seed workflow to parse sources like STATUS.md and security audit reports. This process organizes extracted items into a searchable vault categorized by decisions, tech facts, issues, and sprint records.
The best way to bootstrap a project management knowledge base from scattered markdown files is to run an automated seeding process. This imports existing project documentation and transforms dispersed notes into a structured, searchable vault of institutional memory.
Yes, you can populate a PM vault using STATUS.md and KNOWN_ISSUES.md files. The seeding workflow specifically targets these project documentation sources to extract sprint data, known issues, and decisions, organizing them into structured knowledge records.
You refresh and enrich a project knowledge base when new audit reports are added by re-running the PM seed workflow. This applies the extraction process to new documents, continuously updating the vault with recent tech facts, issues, and decisions.
Yes, the PM seed workflow supports importing sprint data from PROJECT_STATE_REVIEW documents. It extracts sprint records alongside decisions and issues from these existing documentation sources to populate the project management vault.
Seeding a vault from existing docs automates extraction from sources like STATUS.md and audit reports, capturing institutional memory instantly. Manual entry is slower and risks losing scattered decisions, whereas seeding organizes tech facts and issues into a searchable structure immediately.
wangjiawei508Generate construction monitoring reports and risk analysis from project data.
LopeWaleExtract structured PM decisions from sprint reports and project artifacts.
dug-21Automate GitHub issue triage, board synchronization, and sprint tracking.
4lermanSave knowledge entries to auto-memory with timestamp and context.
