Load PRD, FRD, Tech Spec, or RFC into context
67
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/product-design/skills/ctx/SKILL.mdCategory: Context Management
/ctx <doc-reference><doc-reference>: Required - Document identifier or path. Accepts:
PRD-001, FRD-042, TS-0045, RFC-0042user-auth, payment-gateway./product-docs/prds/active/user-auth-prd.mdWhen this command is run, Claude Code should:
Identify Document Type and Location
Search order by ID prefix:
| Prefix | Type | Search Locations |
|---|---|---|
PRD- | Product PRD | product-docs/prds/ |
FRD- | Feature PRD | product-docs/prds/ |
TS- | Tech Spec | tech-specs/ |
RFC- | RFC | rfcs/ |
If no prefix, search all locations for partial name match.
Search for Document
# Search patterns by type
PRD/FRD: product-docs/prds/**/*<query>*.md
Tech Spec: tech-specs/**/*<query>*.md
RFC: rfcs/**/*<query>*.mdHandle Multiple Matches
If multiple documents match, display options:
Multiple documents match "auth":
1. PRD-001-user-authentication-prd.md (PRD)
2. FRD-015-oauth-integration-frd.md (FRD)
3. TS-0044-auth-implementation.md (Tech Spec)
4. RFC-0043-auth-redesign.md (RFC)
Which document to load? [1-4]Read and Present Document
Read the full document content and present with context header:
═══════════════════════════════════════════════════════════
📄 CONTEXT LOADED: PRD-001 - User Authentication System
═══════════════════════════════════════════════════════════
Type: Product PRD
Status: ACTIVE
Version: 1.2
Location: product-docs/prds/active/PRD-001-user-authentication-prd.md
Related Documents:
- Tech Spec: TS-0044-auth-implementation.md
- Tasks: tasks/PRD-001-tasks.md
───────────────────────────────────────────────────────────
[Full document content here]
═══════════════════════════════════════════════════════════
Context loaded. Ready to work on this document.
═══════════════════════════════════════════════════════════Extract Related Documents
Parse the loaded document for references to other documents:
Offer to load related documents:
💡 Related documents found:
- RFC-0043 (linked)
- TS-0044 (implementation spec)
Load related? [y/N]Support loading multiple documents at once:
# Load multiple by ID
/ctx PRD-001 RFC-0043
# Load all related to a PRD
/ctx PRD-001 --related
# Load PRD with its tech spec and tasks
/ctx PRD-001 --full| Option | Description |
|---|---|
--related | Also load all related/linked documents |
--full | Load document + tech spec + tasks |
--summary | Show only metadata and overview, not full content |
Loads complete document content into context.
--summary)📄 PRD-001: User Authentication System
Status: ACTIVE | Version: 1.2 | Progress: 67%
Overview:
Implement secure user authentication with OAuth 2.0 support,
including social login providers and MFA capabilities.
Key Sections:
- User Stories (12 items)
- Technical Requirements (8 items)
- Success Metrics (5 KPIs)
Use '/ctx PRD-001' for full content.Infer document type from:
Filename patterns
*-prd.md → Product PRD*-frd.md → Feature PRDTS-* → Tech SpecRFC-* → RFCDirectory location
product-docs/prds/ → PRD/FRDtech-specs/ → Tech Specrfcs/ → RFCFrontmatter type field
type: product-prd | feature-frd | tech-spec | rfcDocument not found: Show search suggestions
Document "auth-prd" not found.
Did you mean:
- user-authentication-prd.md
- oauth-auth-frd.md
Or search all docs: /list-prds, /list-tech-specs, /list-rfcsInvalid path: Suggest correct format
Empty document: Warn and show metadata only
# Load by document ID
/ctx PRD-001
/ctx RFC-0043
/ctx TS-0044
# Load by partial name
/ctx user-auth
/ctx payment-gateway
# Load by path
/ctx ./product-docs/prds/active/user-auth-prd.md
# Load with related documents
/ctx PRD-001 --related
# Load full context (PRD + tech spec + tasks)
/ctx PRD-001 --full
# Quick overview only
/ctx PRD-001 --summary
# Load multiple documents
/ctx PRD-001 RFC-0043 TS-0044/ctx PRD-001 && /generate-tasks0ebe7ae
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.