prime-feat

Load planning artifacts and context for a feature from backlog directories.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ianphil/prism --skill prime-feat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prime-feat
Source: https://github.com/ianphil/prism/tree/main/.claude/skills/prime-feat
Command: npx skills add https://github.com/ianphil/prism --skill prime-feat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rapid retrieval of all planning artifacts and context for a specific feature, so teams can resume work without hunting through backlog documents.

Core Features & Use Cases

  • Artifact aggregation: Locate and assemble project planning docs for a given feature from backlog/plans and backlog/plans/_completed.
  • Context loading: Gather analysis.md, spec.md, plan.md, data-model.md, tasks.md, and contracts for review or execution.
  • Use Case: When a product manager needs to reopen a feature discussion, quickly load all relevant documents and show the current status.

Quick Start

Use the prime-feat skill to load all planning artifacts for feature {{feature_number}}.

Frequently Asked Questions about prime-feat

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

FAQPage Schema
How do I load planning artifacts for a specific feature number?

Loading feature context requires a known feature number. The system retrieves planning documents including analysis.md, spec.md, plan.md, data-model.md, tasks.md, and contracts from both active and completed backlog/plans directories.

Can I retrieve completed feature planning documents for backlog grooming?

Yes, for backlog grooming the system retrieves completed feature artifacts from backlog/plans/_completed/{{feature_number}}-*/. It aggregates analysis.md, spec.md, plan.md, data-model.md, and tasks.md to review past feature work.

What planning documents are included when loading feature context?

Feature context includes analysis.md, spec.md, plan.md, data-model.md, tasks.md, and all files in contracts/. It also reads test specifications from specs/tests/{{feature_number}}-*.md for comprehensive feature review.

Does loading feature context check the git status of a feature branch?

Yes, checking git status is integrated into feature context loading. The system checks git status for feature/{{feature_number}}-* branches to provide current implementation status alongside the planning documents.

What is the best way to prepare for a feature handoff using planning artifacts?

For a feature handoff, loading all planning artifacts by feature number provides the complete context. This aggregates spec.md, plan.md, data-model.md, tasks.md, and contracts so the receiving team can resume work immediately.