speckit-adlc-product-link

Locate and link Feature PDRs to feature specifications via priority search.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-adlc-product-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-adlc-product-link
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/speckit-adlc-product-link
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-adlc-product-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finding and linking the correct Feature PDR to a feature specification can be tedious and error-prone when PDRs are scattered across multiple locations.

Core Features & Use Cases

  • Silent if no PDRs exist: If no PDRs are present, the tool exits without output to avoid noise.
  • Feature PDR linkage: Locate and reference a Feature PDR for a given feature, ensuring traceability.
  • Priority search: Look for PDRs in the recommended locations in this order: {TEAM_DIRECTIVES}/context_modules/pdr.md (when configured), {REPO_ROOT}/.specify/memory/pdr.md, and {REPO_ROOT}/.specify/drafts/pdr.md.
  • Output results: Returns Milestone and Feature PDR references suitable for populating the spec header.

Quick Start

Run the before_specify hook to locate a Feature PDR, link it to the feature, and apply the Milestone and PDR references to the spec header.

Frequently Asked Questions about speckit-adlc-product-link

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

FAQPage Schema
How do I link a Feature PDR to a feature specification automatically?

To link a Feature PDR to a feature specification, use a hook that searches for PDRs in team directives, repo memory, and drafts, then outputs the Milestone and PDR references for the spec header.

What is the search priority order for finding Feature PDRs in a repository?

The search priority for Feature PDRs checks {TEAM_DIRECTIVES}/context_modules/pdr.md first, then {REPO_ROOT}/.specify/memory/pdr.md, and finally {REPO_ROOT}/.specify/drafts/pdr.md to locate matching documents.

What happens when no matching Feature PDRs are found during spec linkage?

When no matching Feature PDRs are found, the process exits silently with no output to avoid noise and keep your workflow clean.

Can I select a specific Feature PDR when multiple matches exist?

Yes, when multiple matching Feature PDRs exist, the tool presents options for selection, allowing you to choose the correct one to output the Milestone and PDR references.

Do I need a configured team directives path to locate Feature PDRs?

No, you do not need configured team directives. If the {TEAM_DIRECTIVES} path is not configured, the search falls back to {REPO_ROOT}/.specify/memory/pdr.md and drafts/pdr.md.