pm-link

Link PM decisions to related records in decision registers.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill pm-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-link
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-link
Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connects decisions across sprints, issues, and architecture notes and updates decision registers to preserve the institutional memory of software governance.

Core Features & Use Cases

  • Discover connections between decisions and related records to surface dependencies and rationale.
  • Update decision registers and add inline wiki-links to improve traceability and navigation.
  • Use case: When a sprint results in a new architectural decision, link it to the related decisions, issues, and previous implementations to capture provenance.

Quick Start

Provide a target decision name to discover its connections and automatically update the relevant decision registers.

Frequently Asked Questions about pm-link

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

FAQPage Schema
How do I trace architectural decisions back to related issues and sprints?

Trace architectural decisions by discovering relationships between the target decision and related records in registers, applying connections to issues and sprints to enable provenance across the decision graph.

What is the best way to update decision registers with provenance and wiki-links?

Update decision registers by identifying decision relationships, adding inline wiki-links for navigation, and ensuring each connection passes the articulation test to preserve institutional memory.

How do I link sprint results to previous architecture notes and implementations?

Link sprint results to previous architecture notes by discovering dependencies between the new decision and related records, then updating the corresponding decision registers with captured context.

Can I apply decision linking to issues and architecture notes simultaneously?

Apply decision linking to issues, sprints, and architecture notes simultaneously by discovering relationships across the target decision and related records to surface dependencies and rationale.

Why does decision traceability require an articulation test for connections?

Decision traceability requires an articulation test to ensure each connection between decisions and related records is valid, maintaining a coherent PM graph and preserving software governance context.

When do I need to connect decisions across sprints and architecture notes?

Connect decisions across sprints and architecture notes when a sprint results in a new architectural decision, linking it to related decisions and previous implementations to capture provenance.