ring:pre-dev-feature-map

Map PRD features into business-focused feature maps with domains and journeys.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-feature-map
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ring:pre-dev-feature-map
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/pre-dev-feature-map
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-feature-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to mapping PRD features into a business-focused feature map, ensuring teams agree on scope and relationships before diving into technical architecture.

Core Features & Use Cases

  • Feature discovery: extract PRD features and categorize them into Core, Supporting, Enhancement, and Integration.
  • Domain grouping: organize features by business capability domains to reduce cross-domain dependencies.
  • Journey mapping: outline primary user journeys and cross-feature touchpoints to identify handoffs.
  • Gate 2 readiness: establish boundaries, priorities, and integration points to inform TRD planning.
  • Use Case: a product team uses the map to align stakeholders on feature boundaries before TRD.

Quick Start

  1. Gather an approved PRD (Gate 1) and identify all features.
  2. Create docs/pre-dev/{feature-name}/feature-map.md and fill sections for Overview, Feature Inventory, Domain Groupings, User Journeys, Interactions, Phasing, and Boundaries.
  3. Document domains, features, journeys, and priorities to prepare for Gate 2 validation.

Frequently Asked Questions about ring:pre-dev-feature-map

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

FAQPage Schema
How do I map PRD features into a business-focused feature map before architecture?▼

A feature map visualizes the PRD feature landscape by grouping features into business domains and outlining user journeys. This establishes scope boundaries, cross-feature interactions, and priorities before TRD planning.

When do I need to create a feature map for product planning?▼

You need to create a feature map during Gate 2 planning for large features with complex interactions across domains and journeys. It ensures stakeholders agree on scope and relationships before diving into technical architecture.

How do I organize PRD features by domain and user journeys?▼

Document features, domains, journeys, and priorities in a feature-map.md file under docs/pre-dev/{feature-name}/. Fill sections for Overview, Feature Inventory, Domain Groupings, User Journeys, Interactions, Phasing, and Boundaries to prepare for Gate 2 validation.

Does Gate 2 planning require an approved PRD before mapping features?▼

Yes, Gate 2 planning requires an approved PRD from Gate 1 as a prerequisite. You must gather the approved PRD and identify all features before categorizing them and establishing boundaries for TRD readiness.

What's the best way to establish feature boundaries before TRD planning?▼

Mapping PRD features before TRD planning is limited to large features with complex interactions across domains. For simple, isolated features, this structured Gate 2 mapping process may be unnecessary overhead.