gen-feature-journey

Generates feature list and user journey documents from system design specs via a sub-agent.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Samind-Samind/projexa --skill gen-feature-journey-samind-samind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gen-feature-journey
Source: https://github.com/Samind-Samind/projexa/tree/main/.claude/skills/gen-feature-journey
Command: npx skills add https://github.com/Samind-Samind/projexa --skill gen-feature-journey-samind-samind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually synthesizing a feature list with MoSCoW prioritization and user journey flowcharts from dozens of screen spec documents is slow and error-prone. This Skill automates that synthesis for the Projexa project, producing consistent, traceable Markdown documents from existing design sources. ## Core Features & Use Cases - Feature List Generation: Creates or updates docs/01-requirements/feature-list.md with MoSCoW prioritization derived from the system design document, 26 screen specs, and the backlog. - User Journey Generation: Produces docs/02-design/01-prototypes/user-journey.md containing mermaid flowchart diagrams per user journey. - Sub-Agent Orchestration: Delegates content synthesis to the requirements-synthesizer sub-agent while the Skill controls file paths, header templates, index updates, and daily log entries. - Use Case: After updating screen specs in docs/01-requirements/01-spec, run this Skill to regenerate both summary documents, refresh index wikilinks, and record the change in the daily log. ## Quick Start Regenerate the feature list and user journey documents from the current Projexa system design document and screen specs.

Frequently Asked Questions about gen-feature-journey

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

FAQPage Schema
How do I generate a feature list from system design documents?▼

Invoke this Skill after confirming Projexa-System-Design-R1.md, the screen specs in docs/01-requirements/01-spec, and backlog.md exist. It calls the requirements-synthesizer sub-agent and writes feature-list.md with a fixed header template and MoSCoW labels.

How to create user journey diagrams with mermaid flowcharts?▼

The Skill writes user-journey.md containing mermaid flowchart diagrams synthesized by the sub-agent from the design document section 9. Flowchart type is used instead of journey to avoid unsupported satisfaction scores.

Does this Skill write new requirement documents from scratch?▼

No. It only regenerates summary views from existing source documents such as the system design file, screen specs, and backlog. Source of truth remains the individual spec files, and generated files are marked as unconfirmed drafts.

What happens if the sub-agent output format is wrong?▼

The Skill checks for the three required output blocks FEATURE_LIST, USER_JOURNEY, and SOURCES. If any block is missing or malformed, it re-invokes the sub-agent with the problem described rather than fixing content itself.

Will regenerating overwrite existing feature-list or user-journey files?▼

Yes, existing target files are overwritten directly without archiving. This is intentional because the documents are regenerable summary views and git history serves as the versioning layer.