business-problem-to-blueprint

将业务问题转化为软件蓝图

将任何枯燥的 B2B 业务问题转化为完整、可构建的软件解决方案蓝图。

此技能的作用

你只需描述一个业务问题（例如：“一家健身房需要管理私人教练、日程安排和客户签到”），此技能就会生成一个完整的 CLAUDE.md 文件，其中包含：

✅ 软件架构 - 高层系统设计
✅ 数据库架构 - 表、关系和数据结构
✅ 功能拆解 - 按 MVP、第 2 阶段、第 3 阶段组织
✅ 技术栈建议 - 针对特定问题推荐最合适的技术
✅ 分步实施计划 - 为 Claude Code 排定任务顺序
✅ 预计构建时间 - 现实的时间预期
✅ 部署策略 - 如何发布和托管软件

适用对象

需要完成以下工作的软件定制顾问：

• 将客户的问题转化为技术规格
• 无需成为开发者即可制定专业的项目计划
• 为 Claude Code 提供清晰、结构化的指示
• 估算项目范围和复杂度
• 向非技术客户介绍技术解决方案

如何使用此技能

输入格式

用通俗的英文描述业务问题：

输入示例：

Business: Fire inspection company
Problem: They manage 200+ inspections per month using Excel spreadsheets and paper forms. Inspectors waste 2 hours per day on paperwork. Office staff can't track which buildings are due for re-inspection. Clients call constantly asking for reports.

Key Requirements:
- Schedule and assign inspections to field inspectors
- Mobile app for inspectors to complete reports on-site
- Automatic reminders for upcoming inspections
- Generate PDF reports for clients
- Dashboard showing inspection status

输出格式

此技能会生成一个完整的 CLAUDE.md 文件，结构如下：

# [Project Name] - Software Blueprint

## Project Overview
[Clear description of what you're building and why]

## Target Users
[Who will use this software]

## Core Problem Being Solved
[The specific pain points this addresses]

## Software Architecture

### System Components
1. **Frontend Application**
   - User interface for office staff
   - Mobile app for field workers

2. **Backend API**
   - Business logic and data management
   - Authentication and permissions

3. **Database**
   - Data storage and relationships

4. **Integrations**
   - Third-party services needed

### Tech Stack Recommendation
- **Frontend:** [Technology + why it's best for this project]
- **Backend:** [Technology + why]
- **Database:** [Technology + why]
- **Hosting:** [Platform + why]
- **Mobile:** [Approach + why]

## Database Schema

### Tables and Relationships

**inspections**
- id (primary key)
- building_id (foreign key → buildings)
- inspector_id (foreign key → users)
- scheduled_date
- status (scheduled, in_progress, completed)
- due_date
- created_at

**buildings**
- id (primary key)
- name
- address
- client_id (foreign key → clients)
- inspection_frequency (monthly, quarterly, annual)
- last_inspection_date
- next_inspection_due

[... complete schema with all tables]

### Relationships
- One building → Many inspections
- One inspector → Many inspections
- One client → Many buildings

## Feature Breakdown

### MVP Features (Phase 1) - Must-Have for Launch
**Estimated Build Time: 40-60 hours**

1. **User Authentication & Roles**
   - Admin login
   - Inspector login
   - Role-based permissions

2. **Building Management**
   - Add/edit/delete buildings
   - Store client information
   - Set inspection frequency

3. **Inspection Scheduling**
   - Create new inspections
   - Assign to inspectors
   - View upcoming inspections

4. **Basic Inspection Form**
   - Mobile-friendly checklist
   - Pass/fail items
   - Photo upload
   - Notes field

5. **Simple Dashboard**
   - Today's inspections
   - Overdue inspections
   - Inspector availability

### Phase 2 Features - Enhanced Functionality
**Estimated Build Time: 20-30 hours**

1. **PDF Report Generation**
   - Branded inspection reports
   - Photo attachments
   - Digital signatures

2. **Automated Reminders**
   - Email notifications for upcoming inspections
   - SMS alerts for inspectors
   - Client notification when inspection complete

3. **Advanced Dashboard**
   - Analytics and metrics
   - Revenue tracking
   - Inspector performance

### Phase 3 Features - Nice-to-Haves
**Estimated Build Time: 15-20 hours**

1. **Client Portal**
   - Clients can view their inspection history
   - Download past reports
   - Request new inspections

2. **Route Optimization**
   - Suggest efficient inspection routes
   - Map view of scheduled inspections

3. **Invoice Generation**
   - Automatic invoicing after inspection
   - Payment tracking

## Step-by-Step Implementation Plan

### Week 1: Foundation Setup
**Tasks for Claude Code:**

1. **Project Initialization**
   - "Set up a Next.js project with TypeScript and Tailwind CSS"
   - "Configure Supabase for database and authentication"
   - "Create basic folder structure: /components, /pages, /lib, /types"

2. **Database Setup**
   - "Create Supabase tables: users, buildings, clients, inspections"
   - "Set up row-level security policies for multi-tenant access"
   - "Create database relationships and foreign keys"

3. **Authentication**
   - "Implement Supabase authentication with email/password"
   - "Create login and signup pages"
   - "Add role-based middleware for admin vs inspector access"

### Week 2: Core Features
**Tasks for Claude Code:**

1. **Building Management**
   - "Create a buildings list page with search and filter"
   - "Build add/edit building form with client assignment"
   - "Implement CRUD operations for buildings"

2. **Inspection Scheduling**
   - "Create inspection scheduling interface"
   - "Build inspector assignment dropdown"
   - "Add calendar view of scheduled inspections"

[... detailed week-by-week breakdown continues]

## Deployment Strategy

### Recommended Hosting
- **Frontend + Backend:** Vercel (seamless Next.js deployment)
- **Database:** Supabase (managed PostgreSQL)
- **File Storage:** Supabase Storage (for photos)
- **Domain:** Client's domain via Vercel custom domains

### Deployment Steps
1. Push code to GitHub repository
2. Connect Vercel to GitHub repo
3. Configure environment variables in Vercel
4. Deploy production build
5. Set up custom domain (client's domain)

### Estimated Costs
- **Hosting:** $20/month (Vercel Pro + Supabase Pro)
- **Domain:** $12/year
- **Total Monthly Cost:** ~$20-25

## Testing & Quality Assurance

### Pre-Launch Checklist
- [ ] All user roles tested (admin, inspector)
- [ ] Mobile responsiveness verified
- [ ] Forms validate correctly
- [ ] Database backups configured
- [ ] Error handling implemented
- [ ] Loading states on all actions
- [ ] Client data secure and isolated

## Handoff to Client

### Training Materials Needed
- Admin user guide (how to add buildings, schedule inspections)
- Inspector user guide (how to complete inspections on mobile)
- Video walkthrough of core features

### Support Plan
- 30-day bug fix guarantee included
- Optional monthly maintenance package ($500-1500/month)

## Project Timeline Summary

**Total Estimated Build Time:** 75-110 hours
- MVP (Phase 1): 40-60 hours → 2-3 weeks
- Phase 2: 20-30 hours → 1-2 weeks
- Phase 3: 15-20 hours → 1 week

**Realistic Client Timeline:** 4-6 weeks from kickoff to launch

## Pricing Recommendation

Based on complexity and value delivered:
- **MVP Only:** $12,000 - $15,000
- **MVP + Phase 2:** $18,000 - $22,000
- **Full Build (All Phases):** $25,000 - $35,000

**Justification:**
- Saves 2 hours/day × 5 inspectors = 50 hours/week saved
- At $30/hour labor cost = $1,500/week saved
- Software pays for itself in 10-15 weeks
- Annual savings: $78,000

## Next Steps

1. **Review this blueprint with client** - Confirm it matches their needs
2. **Prioritize features** - Decide which phase to start with
3. **Sign contract** - Lock in scope and pricing
4. **Begin development** - Use this CLAUDE.md file to guide Claude Code
5. **Weekly check-ins** - Show progress and get feedback

---

**This blueprint is ready to use as your CLAUDE.md project instruction file. Simply copy this into your project and start building with Claude Code.**

最佳实践

创建蓝图时

应该：

• ✅ 针对边缘情况提出澄清问题
• ✅ 尽早确定技术限制（集成、合规性）
• ✅ 将复杂功能拆分为更小、可构建的部分
• ✅ 提供切合实际的时间估算
• ✅ 建议分阶段交付，以降低风险
• ✅ 考虑移动设备／平板电脑的使用模式
• ✅ 考虑数据安全和隐私

不应该：

• ❌ 过度设计解决方案
• ❌ 毫无理由地推荐前沿技术
• ❌ 承诺需要定制硬件才能实现的功能
• ❌ 忽视不断发展的企业对可扩展性的需求
• ❌ 忘记用户角色和权限

常见业务问题模式

排程与调度：

• 上门服务企业（暖通空调、管道维修、检查）
• 医疗预约
• 配送路线管理

库存与资产跟踪：

• 建筑设备
• 租赁业务
• 仓库管理

客户／项目管理：

• 代理机构和咨询公司
• 自由职业者工作流
• 承包商任务跟踪

表单数字化：

• 用移动数据采集取代纸质表单
• 检查清单
• 审计与合规报告

内部工具：

• 员工工时跟踪
• 资源分配
• 审批工作流

输出质量标准

每份蓝图都必须包含：

• ✅ 清晰的问题陈述
• ✅ 完整的数据库架构
• ✅ 含时间估算的分阶段功能拆解
• ✅ 具体的技术栈及推荐理由
• ✅ 分步实施计划
• ✅ 现实的定价建议
• ✅ 用于向客户说明方案合理性的投资回报率（ROI）计算

与开发工作流集成

此蓝图将成为实际构建项目时使用的 CLAUDE.md 文件：

1. 将蓝图保存为 CLAUDE.md，放在项目根目录
2. 打开 Claude Code 并引用此文件
3. 从实施计划中复制／粘贴任务
4. 按照蓝图逐项构建功能
5. 随着进度勾选已完成的项目

请记住

你创建的不只是一份技术规格，更是一份软件产品的商业计划。每项功能都应解决实际问题并带来可衡量的价值。蓝图应让客户说出：“没错，这正是我们需要的，花 15K 美元很值得。”