project-artifact-linker

Extract structured entities from project documents and generate cross-reference traceability reports.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill project-artifact-linker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-artifact-linker
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/project-artifact-linker
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill project-artifact-linker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Project artifacts like WBS plans, meeting minutes, requirements, and decisions often live in separate files, making it hard to prove which decisions and requirements drove which deliverables and tasks.

Core Features & Use Cases

  • Extract structured entities from documents: Pull meetings (dates, attendees, action items, decisions), WBS tasks (IDs, names, owners, dates), requirements (IDs, descriptions, priorities), and decision logs into JSON.
  • Create cross-reference links across artifact types: Map action items → WBS tasks, decisions → requirements, meetings → WBS tasks, and requirements → WBS tasks with confidence scoring for review.
  • Generate traceability reports and gap analysis: Produce human-readable Markdown and/or JSON reports, including orphaned requirements, tasks, decisions, and action items.

Quick Start

Use the project-artifact-linker skill to link your project documents in /path/to/project/docs and generate a traceability_report.md and coverage_analysis.json.

Frequently Asked Questions about project-artifact-linker

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

FAQPage Schema
How do I build traceability between project meetings, WBS plans, and requirements?

Build traceability by extracting structured entities from project documents and mapping action items, decisions, and requirements to WBS tasks using deterministic parsing scripts that generate JSON links and Markdown reports.

How do I identify orphaned requirements and decisions in project documentation?

Identify orphaned requirements and decisions by running gap analysis scripts that cross-reference extracted entities across a document corpus, producing a coverage report that highlights unlinked artifacts.

Can I generate compliance evidence from scattered project artifacts for an audit?

Generate compliance evidence for audits by parsing meeting minutes and WBS plans to construct a traceability map, outputting structured JSON files and human-readable Markdown reports that prove decision-to-deliverable linkage.

Does project-artifact-linker work with Markdown and JSON file formats?

The skill works with Markdown and JSON file formats by using deterministic scripts to parse raw project documents into JSON entities and generating final traceability reports in both Markdown and JSON structures.

What is the best way to map action items to WBS tasks with confidence scoring?

Map action items to WBS tasks by extracting structured entities from documents and applying deterministic link construction algorithms that assign confidence scores to each cross-reference for later review.

Do I need to install pyyaml to parse project documents for traceability reporting?

You need to install the pyyaml dependency to run the deterministic scripts that parse raw project documents, extract structured entities, and execute the link construction logic for traceability reporting.