b2c-android-prd

Generate Markdown PRD documents from B2C Android feature module structures.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-android-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-android-prd
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-Android/prd
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-android-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tooling automates creation of PRD documents for B2C Android feature modules by analyzing feature module names, code structure, and PRD templates, reducing manual planning time and improving consistency across projects.

Core Features & Use Cases

  • Analyze feature/{name}/ and common Screen/Route/ViewModel/Contract patterns to determine PRD content.
  • Generate .docs/prd/{feature-name}.md with sections like overview, screen specs, data loading, state management, side effects, API endpoints, and navigation details.
  • Use case: When starting a new B2C feature module, run the tool to produce a ready-to-update PRD that teams can reference.

Quick Start

Run the PRD generation workflow for a target feature module by executing the tool with the feature path (e.g., /prd {feature-name}) to create or update the PRD file.

Frequently Asked Questions about b2c-android-prd

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

FAQPage Schema
How do I generate a PRD for an Android feature module?

You generate a PRD for an Android feature module by executing the tool with the target feature path, which analyzes the codebase structure and automatically outputs a production-ready Markdown PRD.

What is automated PRD generation for B2C Android features?

Automated PRD generation for B2C Android features is a workflow that analyzes your feature module's codebase and naming conventions to produce a Markdown document containing overviews, UI specs, data flow, and navigation details.

Does PRD generation work with Screen, Route, ViewModel, and Contract patterns?

Yes, PRD generation applies specifically to feature modules using Screen, Route, ViewModel, and Contract patterns, reading the module structure to determine the PRD content and output accurate screen specs.

Can I use this to document data loading and state management for Android features?

Yes, you can use this to document data loading and state management, as the generated PRD includes sections for state management, side effects, API endpoints, and data flow derived directly from the feature codebase.

What's the best way to create consistent PRD documents across multiple Android projects?

The best way to create consistent PRD documents across Android projects is to automate PRD generation by analyzing feature module structures, ensuring uniform documentation formatting and reducing manual planning time.

What sections are included in an auto-generated Android feature PRD?

An auto-generated Android feature PRD includes sections for overviews, screen specs, data loading, state management, side effects, API endpoints, and navigation details, all formatted within a single Markdown file.