|
|
--- |
|
|
title: "Project Description Format (PRD-Style)" |
|
|
type: "project_charter" |
|
|
version: "1.0" |
|
|
created_by: "AI Development Assistant" |
|
|
last_updated: "<DATE>" |
|
|
--- |
|
|
|
|
|
# Project Description Format Template |
|
|
|
|
|
## π Project Metadata |
|
|
```yaml |
|
|
project_id: "<UNIQUE_PROJECT_ID>" |
|
|
project_name: "<PROJECT_NAME>" |
|
|
version: "<SEMVER_VERSION>" |
|
|
status: "planning|in_progress|completed|on_hold" |
|
|
priority: "critical|high|medium|low" |
|
|
category: "hackathon|product|research|prototype" |
|
|
timeline: |
|
|
start_date: "<YYYY-MM-DD>" |
|
|
target_completion: "<YYYY-MM-DD>" |
|
|
estimated_duration: "<X_days>" |
|
|
stakeholders: |
|
|
- project_lead: "<NAME>" |
|
|
- tech_lead: "<NAME>" |
|
|
- contributors: ["<NAME1>", "<NAME2>"] |
|
|
repositories: |
|
|
- primary: "<GITHUB_URL>" |
|
|
- auxiliary: ["<URL1>", "<URL2>"] |
|
|
``` |
|
|
|
|
|
## π― Project Vision & Problem Statement |
|
|
|
|
|
### **Problem Statement** |
|
|
<!-- Clear, concise description of the problem being solved --> |
|
|
**Problem:** <ONE_SENTENCE_PROBLEM_DESCRIPTION> |
|
|
|
|
|
**Pain Points:** |
|
|
- Primary pain point impacting <STAKEHOLDER_GROUP> |
|
|
- Secondary challenges in current solutions |
|
|
- Market/technical gaps being addressed |
|
|
|
|
|
### **Vision Statement** |
|
|
<!-- Inspiring, future-focused statement of what success looks like --> |
|
|
**Vision:** <ASPIRATIONAL_ONE_SENTENCE_VISION> |
|
|
|
|
|
**Success Metrics:** |
|
|
- Primary KPI: <MEASURABLE_OUTCOME> |
|
|
- Secondary metrics: <ADDITIONAL_METRICS> |
|
|
- Qualitative goals: <USER_EXPERIENCE_GOALS> |
|
|
|
|
|
## ποΈ Technical Architecture & Approach |
|
|
|
|
|
### **Technology Stack** |
|
|
```yaml |
|
|
languages: ["Python", "JavaScript", "etc"] |
|
|
frameworks: ["FastAPI", "Gradio", "etc"] |
|
|
infrastructure: ["HuggingFace Spaces", "GitHub Actions", "etc"] |
|
|
apis_integrations: ["OpenAI", "Anthropic", "HF Inference", "etc"] |
|
|
development_tools: ["uv", "ruff", "mypy", "pytest", "just"] |
|
|
``` |
|
|
|
|
|
### **Architecture Principles** |
|
|
- **Modularity:** Component-based design with clear interfaces |
|
|
- **Scalability:** Built to handle growth in [specific dimension] |
|
|
- **Maintainability:** Code quality standards and comprehensive testing |
|
|
- **Integration:** Seamless API and service integrations |
|
|
- **User Experience:** [UX principle specific to project] |
|
|
|
|
|
### **Core Components** |
|
|
1. **Component Name 1:** Brief description and primary responsibility |
|
|
2. **Component Name 2:** Brief description and primary responsibility |
|
|
3. **Component Name 3:** Brief description and primary responsibility |
|
|
|
|
|
## π MVP Strategy & Delivery Plan |
|
|
|
|
|
### **MVP Progression Strategy** |
|
|
``` |
|
|
MVP1 β MVP2 β MVP3 β MVP4 β MVP5 |
|
|
β β β β β |
|
|
Base Enhanced Advanced Real Innovation |
|
|
``` |
|
|
|
|
|
### **Value Delivery Timeline** |
|
|
| MVP | Duration | Core Value Delivered | Demo-able Outcome | |
|
|
|-----|----------|----------------------|-------------------| |
|
|
| MVP1 | <TIMEFRAME> | <PRIMARY_VALUE> | <DEMO_DESCRIPTION> | |
|
|
| MVP2 | <TIMEFRAME> | <PRIMARY_VALUE> | <DEMO_DESCRIPTION> | |
|
|
| MVP3 | <TIMEFRAME> | <PRIMARY_VALUE> | <DEMO_DESCRIPTION> | |
|
|
| MVP4 | <TIMEFRAME> | <PRIMARY_VALUE> | <DEMO_DESCRIPTION> | |
|
|
| MVP5 | <TIMEFRAME> | <PRIMARY_VALUE> | <DEMO_DESCRIPTION> | |
|
|
|
|
|
### **Risk Mitigation Strategy** |
|
|
- **Technical Risks:** <PRIMARY_TECH_RISK> β <MITIGATION_APPROACH> |
|
|
- **Timeline Risks:** <SCHEDULE_RISK> β <CONTINGENCY_PLAN> |
|
|
- **Integration Risks:** <INTEGRATION_RISK> β <FALLBACK_STRATEGY> |
|
|
|
|
|
## ποΈ Development Workflow & Standards |
|
|
|
|
|
### **Development Process** |
|
|
- **Methodology:** Iterative MVP development with AI-assisted coding |
|
|
- **Sprint Cycle:** <SPRINT_LENGTH> sprints with <DELIVERY_FREQUENCY> |
|
|
- **Quality Gates:** Automated testing, linting, type checking, CI/CD |
|
|
- **Review Process:** <CODE_REVIEW_STRATEGY> |
|
|
|
|
|
### **Tool Integration** |
|
|
- **Task Management:** GitHub Issues + Projects integration |
|
|
- **Code Quality:** Ruff (linting) + Black (formatting) + MyPy (types) |
|
|
- **Testing:** pytest with coverage tracking |
|
|
- **Automation:** Just recipes for common workflows |
|
|
- **AI Assistance:** Claude/Cursor IDE integration for development |
|
|
|
|
|
### **Standards & Conventions** |
|
|
- **Code Style:** <LINK_TO_STYLE_GUIDE> |
|
|
- **Commit Messages:** Conventional Commits specification |
|
|
- **Documentation:** <DOCUMENTATION_STANDARDS> |
|
|
- **API Design:** <API_DESIGN_PRINCIPLES> |
|
|
|
|
|
## π Success Criteria & Measurement |
|
|
|
|
|
### **Definition of Done (Project Level)** |
|
|
- [ ] All MVP deliverables completed and deployed |
|
|
- [ ] Comprehensive documentation and demos available |
|
|
- [ ] Quality gates passed (>80% test coverage, zero linting errors) |
|
|
- [ ] User acceptance criteria validated |
|
|
- [ ] Production deployment successful |
|
|
- [ ] Post-project review and lessons learned documented |
|
|
|
|
|
### **Key Performance Indicators** |
|
|
- **Functional KPIs:** <FEATURE_COMPLETION_METRICS> |
|
|
- **Quality KPIs:** <CODE_QUALITY_METRICS> |
|
|
- **Performance KPIs:** <SYSTEM_PERFORMANCE_METRICS> |
|
|
- **User KPIs:** <USER_SATISFACTION_METRICS> |
|
|
|
|
|
## π Resources & References |
|
|
|
|
|
### **Documentation Links** |
|
|
- **Architecture Docs:** `docs/architecture/` |
|
|
- **API Documentation:** `docs/api/` |
|
|
- **User Guides:** `docs/user/` |
|
|
- **Developer Setup:** `CONTRIBUTING.md` |
|
|
|
|
|
### **External Dependencies** |
|
|
- **Service Dependencies:** <LIST_OF_EXTERNAL_SERVICES> |
|
|
- **API Credentials:** <CREDENTIAL_MANAGEMENT_STRATEGY> |
|
|
- **Third-party Integrations:** <INTEGRATION_DETAILS> |
|
|
|
|
|
### **Related Projects** |
|
|
- **Similar Solutions:** <COMPETITIVE_ANALYSIS> |
|
|
- **Inspiration Sources:** <REFERENCE_PROJECTS> |
|
|
- **Technical References:** <TECHNICAL_DOCUMENTATION_LINKS> |
|
|
|
|
|
--- |
|
|
|
|
|
## π Template Usage Guidelines |
|
|
|
|
|
### **When to Use This Format** |
|
|
- New project initiation |
|
|
- Project scope definition |
|
|
- Stakeholder alignment |
|
|
- Technical architecture planning |
|
|
- Resource allocation decisions |
|
|
|
|
|
### **Customization Instructions** |
|
|
1. Replace all `<PLACEHOLDER>` values with project-specific information |
|
|
2. Remove sections that don't apply to your project type |
|
|
3. Add project-specific sections as needed |
|
|
4. Update the metadata section with actual dates and stakeholders |
|
|
5. Ensure all links and references are functional |
|
|
|
|
|
### **Integration with Development Workflow** |
|
|
- Link this document from your main README.md |
|
|
- Reference MVPs and sprints defined here in detailed planning docs |
|
|
- Use project metadata for GitHub project configuration |
|
|
- Include success criteria in your CI/CD pipeline validation |
|
|
|
|
|
--- |
|
|
|
|
|
**Document Status:** Template |
|
|
**Next Review:** Before project kickoff |
|
|
**Approval Required:** Project Lead + Tech Lead |