Craig 38d67f3c2f feat: Add collections support with plan collection

✨ New Features:
• Collections system for organizing domain-specific customizations
• Plan collection with 6 specialized prompts for feature development
• Automated README generation for collections
• Badge generation with proper collection path support

📝 Plan Collection Content:
• Epic planning (PRD and architecture)
• Feature planning (PRD and implementation)
• GitHub issue automation
• Build implementation guide
• Comprehensive development workflow

🔧 Script Enhancements:
• Collections discovery and processing
• Individual collection README generation
• Main README collections section
• Badge URL generation with collection paths
• Proper navigation links to README.md files

📁 Structure:
collections/
├── plan/ (6 prompts)
└── test/ (demo content)

The collections feature enables organized, domain-specific GitHub Copilot customizations with automated documentation and proper VS Code integration.

2025-07-30 20:40:54 +02:00

2.2 KiB

Raw Blame History

mode	description
agent	Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

Epic Product Requirements Document (PRD) Prompt

Goal

Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to translate high-level ideas into detailed Epic-level Product Requirements Documents (PRDs). These PRDs will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical architecture specification for the epic.

Review the user's request for a new epic and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the epic are well-defined.

Output Format

The output should be a complete Epic PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/epic.md.

PRD Structure

1. Epic Name

A clear, concise, and descriptive name for the epic.

2. Goal

Problem: Describe the user problem or business need this epic addresses (3-5 sentences).
Solution: Explain how this epic solves the problem at a high level.
Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, revenue)?

3. User Personas

Describe the target user(s) for this epic.

4. High-Level User Journeys

Describe the key user journeys and workflows enabled by this epic.

5. Business Requirements

Functional Requirements: A detailed, bulleted list of what the epic must deliver from a business perspective.
Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).

6. Success Metrics

Key Performance Indicators (KPIs) to measure the success of the epic.

7. Out of Scope

Clearly list what is not included in this epic to avoid scope creep.

8. Business Value

Estimate the business value (e.g., High, Medium, Low) with a brief justification.

Context Template

Epic Idea: [A high-level description of the epic from the user]
Target Users: [Optional: Any initial thoughts on who this is for]

2.2 KiB Raw Blame History