plan

Analyze user requests to extract business rules and generate implementation roadmaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill plan-ryu-qqq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill plan-ryu-qqq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans feature requirements and generates implementation roadmaps by analyzing user requests and extracting business rules.

Core Features & Use Cases

  • Requirement analysis and rule derivation
  • Impact assessment and strategic mapping
  • Roadmap generation to epics and execution tasks
  • Serena Memory persistence for planning context

Quick Start

Plan a new feature by analyzing a user request and outlining its implementation roadmap.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a feature implementation roadmap from user requirements?

Feature planning involves analyzing user requests to extract business rules, performing impact assessments, and mapping strategies across architecture layers. This process generates clear implementation roadmaps with defined epics and execution tasks.

What is Serena Memory used for in product planning workflows?

In product planning workflows, Serena Memory provides persistence for planning context. It stores extracted business rules and impact assessments to maintain continuity and enable clear handoffs to epics and execution tasks.

How do I extract business rules from user requests for requirement analysis?

You can extract business rules by analyzing user requests to identify underlying functional needs and constraints. This requirement analysis process maps the derived rules across architecture layers to build a strategic implementation plan.

Can I use this approach for end-to-end planning from requirements to epics?

Yes, this approach supports end-to-end planning by connecting requirement analysis directly to epics and execution tasks. It satisfies the functional need for clear handoffs by applying strategic mapping across architecture layers.

What is the best way to conduct an impact assessment for feature planning?

The best way to conduct an impact assessment is to map the strategy across architecture layers after extracting business rules from user requests. This ensures comprehensive analysis before generating the implementation roadmap.

Does requirement analysis work without memory persistence for planning context?

Requirement analysis can function without memory persistence, but utilizing Serena Memory ensures that planning context is retained. This allows for better continuity when handing off extracted rules to epics and execution tasks.