Why is mapping features important before coding?

Mapping prevents architectural mismatches, identifies late-stage integration problems early, and ensures module boundaries align with business concerns rather than technical convenience.

Does this skill help with technical architecture?

It provides the business-level context necessary for architecture, but it explicitly forbids technical details like API specs or database schemas to ensure focus remains on feature relationships.

How does this skill handle MVP prioritization?

It includes a mandatory Phasing Strategy section that categorizes features into Core, Supporting, and Enhancement groups to define a clear path to MVP.

When should I use the Feature Map skill?

Use it after a PRD has been validated (Gate 1) but before creating a Technical Requirements Document (TRD), specifically for features with complex interactions or large scope.

Pre-Dev Feature Mapping

Name: Pre-Dev Feature Mapping
Author: LerianStudio

byLerianStudio

•

Productivity & Workflow

Visualizes the business-level feature landscape and relationship map to align architectural planning with product requirements.

This skill implements Gate 2 of the Ring workflow, ensuring that feature boundaries, domain groupings, and user journeys are fully understood before any technical implementation begins. It guides Claude through analyzing a PRD to extract features and map complex interactions, preventing common architectural errors caused by premature technical decisions. By focusing strictly on business-level logic, it creates a foundational blueprint that informs the subsequent technical design phase, ensuring the final architecture perfectly matches the feature scope.

Key Features

01Strategic phasing and prioritization for MVP and incremental delivery

02Automated feature inventory extraction from validated PRDs

03Cross-feature user journey mapping to identify integration points

0417 GitHub stars

05Visual dependency and interaction mapping using ASCII/text diagrams

06Domain-based grouping to define logical business boundaries

Use Cases

01Defining business domains to inform future module or microservice boundaries

02Mapping complex interactions in large-scale feature sets requiring 2+ days of development

03Validating feature scope and dependencies before starting the Technical Requirements Document (TRD)

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lerianstudio/ring pre-dev-feature-map

For use in Claude.ai and ChatGPT

Download Skill