Complete documentation for the Bitinfrashop Bitcoin marketplace connecting infrastructure providers with shops worldwide
- Product Vision - Understand what we're building and why
- Roadmap - See where we're going
- Development Workflow - How we build features
- AI Agent Guidelines - How to work with AI assistants
- Claude Code Setup - Configure Claude Code
- Architecture Decisions - Why we built it this way
- Development Journal - What we've built
- Feature Registry - All features and their status
- Backlog - Current task list
- Problem Statements - User problems we're solving
This documentation follows the BMAD-METHOD inspired framework: a four-phase approach to product development that emphasizes reflection, collaboration, and systematic thinking.
docs/
├── 01-analysis/ # Understanding & Research
├── 02-planning/ # Strategic Planning
├── 03-solutioning/ # Design & Specification
├── 04-implementation/ # Execution & Tracking
├── workflows/ # Process Documentation
└── tools/ # Tool-specific guides
Purpose: Deeply understand problems before proposing solutions
Document user pain points with evidence and success metrics.
Early-stage concepts and brainstorms.
Purpose: Prioritize and strategize feature development
- Product Vision: Our mission and 3-year strategy
- Roadmap: Quarterly feature planning and milestones
- Feature Registry: All features with status and priority
Why we made key technical choices.
Quarterly planning and feature timeline.
Purpose: Design technical solutions with thorough specifications
Detailed design docs for features.
- Template - Use this for new features
- Private Server Invitations
- Browse All Features
Third-party service integration guides.
Purpose: Track execution and document progress
Daily/weekly progress logs.
Sprint planning and retrospectives.
Current tasks and priorities.
Test reports and quality assurance.
Documentation from Geyser NWC Hackathon win.
Purpose: Systematic processes for development activities
- Feature Development - Complete feature lifecycle
- Bug Fix Workflow - Fix and prevent bugs
- Release Process - Ship to production
- AI Agent Guidelines - How AI assistants should work with this codebase
- Claude Code Setup - Configure Claude Code
- Claude Code Configuration - Detailed permission settings
AI-powered development assistant integration.
- README - Overview and use cases
- Configuration - Detailed setup
Guidelines for working with AI assistants.
Use these templates to create consistent documentation:
- Clear & Concise: Get to the point quickly
- Structured: Use headings, lists, and tables
- Actionable: Include next steps and checklists
- Dated: Include creation and update dates
- Linked: Reference related documents
- Review Cadence: Quarterly for strategic docs, monthly for tactical docs
- Ownership: Assign document owners
- Version Control: All docs in git, track changes
- Archival: Move outdated docs to archive folder
- Use kebab-case:
private-server-invitations.md - Prefix ADRs with number:
ADR-001-description.md - Prefix sprints with date:
2025-10-13-sprint-5.md - Use _TEMPLATE for templates:
_TEMPLATE.md
- Create problem statement in
01-analysis/problem-statements/ - Add to feature registry in
02-planning/feature-registry.md - Create specification in
03-solutioning/features/ - Follow Feature Development Workflow
- Use ADR template from
02-planning/architecture-decisions/ADR-000-template.md - Number sequentially (ADR-001, ADR-002, etc.)
- Get team review before marking "Accepted"
- Schedule 6-month reflection review
- Update "Last Updated" date
- Note changes in revision history (if applicable)
- Update related documents with cross-references
- Commit with descriptive message
- README.md - Project overview and setup
- SECURITY.md - Security policy and reporting
- Contact: nodediver@proton.me
- GitHub Issues: Report documentation issues
See AI Agent Guidelines or Development Log
Last Updated: 2025-10-13 Documentation Framework: Inspired by BMAD-METHOD™ Maintained By: Development Team