my_project

/my_project - Project Brief Generator

Create a comprehensive project.md brief through an interactive workflow. This is NOT technical documentation - it defines WHAT the project is and WHY it exists.

Arguments

• No arguments: Full interactive workflow
• --quick: Minimal project brief (name, description, slogan)
• --research: Include market research via idea-research plugin

Output: project.md

A non-technical project brief containing:

• Project identity (name, tagline, description)
• Problem statement (what pain it solves)
• Target audience (who it's for)
• Value proposition (why it's unique)
• Core features (what it does, not how)
• Success metrics (how to measure success)

Workflow

Phase 1: Project Discovery

Check for existing project context:

# Check for existing project.md
ls -la project.md PROJECT.md 2>/dev/null

# Check package.json for name/description
cat package.json 2>/dev/null | head -20

# Check composer.json
cat composer.json 2>/dev/null | head -20

# Check pubspec.yaml
cat pubspec.yaml 2>/dev/null | head -20

Phase 2: Interactive Identity Creation

Ask user for project fundamentals:

PROJECT IDENTITY
================

Let's define your project's core identity.

1. PROJECT NAME
   What is your project called?
   [Detected: "my-app" from package.json]

2. TAGLINE (One sentence)
   A memorable phrase that captures your project's essence.
   Examples:
   - "Build faster, ship sooner"
   - "Your finances, simplified"
   - "The last CRM you'll ever need"

3. DESCRIPTION (2-3 sentences)
   What does your project do? Who is it for?
   Focus on the BENEFIT, not the technology.

   Good: "A task manager that helps busy professionals
         stay organized without the complexity."

   Avoid: "A React app with Redux and PostgreSQL
          that manages tasks."

Phase 3: Problem & Solution

Guide user through problem-solution framing:

PROBLEM STATEMENT
=================

What problem does your project solve?

PROBLEM:
[User describes the pain point]

Good problem statements:
- "Small business owners spend 5+ hours/week on invoicing"
- "Developers waste time switching between 10+ tools"
- "Remote teams lose context in async communication"

WHO EXPERIENCES IT:
[Target user/segment]

IMPACT IF UNSOLVED:
[Business/personal cost of the problem]