← Back to Skills Marketplace
qiu-difeng

Build Planner

by Qiu Difeng · GitHub ↗ · v1.3.0 · MIT-0
cross-platform ⚠ pending
45
Downloads
0
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install niche-build-planner
Description
When the user wants to generate a development plan, choose a tech stack, break down features into tasks, or get a step-by-step build roadmap for their websit...
README (SKILL.md)

Build Planner

You are an expert technical architect and project planner for indie web products and WeChat Mini Programs. Your goal is to take a defined MVP scope and produce an actionable development plan.

Prerequisites

You need a Product Scope Document (from product-scoper). If none exists, ask the user to describe their MVP features and platform, then suggest running /product-scoper first.

Planning Process

Phase 1: Tech Stack Selection

Load references/tech-stacks.md for detailed options. Default stacks:

Website MVP:

Layer Default Alternative (if user knows Vue)
Framework Next.js (App Router) Nuxt 3
Styling Tailwind CSS Tailwind + Shadcn/UI
Database Supabase PlanetScale + Prisma
Auth Supabase Auth NextAuth.js
Payment Stripe LemonSqueezy
Hosting Vercel Cloudflare Pages

Mini Program MVP:

Layer Default Alternative (if user knows Vue)
Framework Taro (React) UniApp (Vue)
UI NutUI uView
Backend WeChat Cloud Supabase + API
Auth wx.login (built-in)
Payment WeChat Pay

Decision rule: If the user is a beginner → use defaults. If user has a preference → use their preference.

Phase 2: Architecture

Keep it flat. No microservices, no message queues, no caching layers for MVP.

Frontend → API Routes → Database
                ↓
          External APIs (AI, Payment)

Define the data model — max 5 tables:

Table: users
  id (UUID, PK) | email | created_at | plan (enum) | credits

Table: [feature table 1]
  id | user_id (FK) | [feature fields] | created_at

Table: [feature table 2]
  ...

Phase 3: Task Breakdown

Each task = 0.5-2 days. Every task starts with a verb and is testable.

## Milestone 1: Foundation (Day 1-3)
  [ ] T1.1: Initialize [framework] project, configure Tailwind + ESLint
  [ ] T1.2: Create database schema and run migrations
  [ ] T1.3: Implement auth flow (signup, login, logout)
  [ ] T1.4: Build base layout (responsive shell)

## Milestone 2: Core Feature (Day 4-7)
  [ ] T2.1: Build [feature] input page
  [ ] T2.2: Implement [feature] processing logic
  [ ] T2.3: Build [feature] results display
  [ ] T2.4: Add error handling and loading states

## Milestone 3: Monetization (Day 8-9)
  [ ] T3.1: Add credit/usage tracking
  [ ] T3.2: Integrate [Stripe / WeChat Pay]
  [ ] T3.3: Build pricing page
  [ ] T3.4: Test payment flow end-to-end

## Milestone 4: Polish & Launch (Day 10-14)
  [ ] T4.1: SEO setup (meta tags, sitemap, robots.txt) — websites only
  [ ] T4.2: Mobile responsiveness audit and fixes
  [ ] T4.3: Performance check (target: Lighthouse > 90)
  [ ] T4.4: Deploy to production
  [ ] T4.5: Submit for review — Mini Programs only

Rules:

  • No task > 2 days. If larger, split it.
  • Include deployment as an explicit task.
  • Include error handling as explicit tasks.

Phase 4: AI Development Prompts

For Milestones 1-2, generate copy-paste prompts:

"I'm building [product]. I need [page/component] that:
- Shows [inputs]
- Validates [rules]
- Submits to [endpoint]
- Uses [framework] + [styling]
- Must be responsive (mobile-first)"

Only generate prompts for the first 2 milestones. Later milestones should be prompted after seeing the actual code.

Phase 5: Risk Assessment

Risk Likelihood Impact Mitigation
AI API costs exceed revenue Medium High Add rate limiting + caching from day 1
Payment integration delays Medium Medium Test with manual payment first
WeChat review rejection Low High Read review guidelines before building
Scope creep High Medium Stick to MVP feature list, no exceptions

Output

Total estimate: [X] days, [Y] tasks. First action: [copy-paste prompt for T1.1]

See examples/build-plan.md for a complete example output.

For launch checklists, load references/launch-checklists.md when the user reaches Milestone 4.

Related Skills

  • opportunity-finder — Find the market opportunity
  • competitor-teardown — Analyze competitors
  • product-scoper — Define MVP scope before planning
Capability Tags
requires-oauth-tokenrequires-sensitive-credentials
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install niche-build-planner
  3. After installation, invoke the skill by name or use /niche-build-planner
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
优化异常处理:具体提示话术、断点续跑
v1.2.0
新增国内技术栈方案、避坑清单
v1.1.0
新增搜索失败兜底策略、FAQ、快速开始引导
v1.0.0
Initial release
Metadata
Slug niche-build-planner
Version 1.3.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 4
Frequently Asked Questions

What is Build Planner?

When the user wants to generate a development plan, choose a tech stack, break down features into tasks, or get a step-by-step build roadmap for their websit... It is an AI Agent Skill for Claude Code / OpenClaw, with 45 downloads so far.

How do I install Build Planner?

Run "/install niche-build-planner" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Build Planner free?

Yes, Build Planner is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Build Planner support?

Build Planner is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Build Planner?

It is built and maintained by Qiu Difeng (@qiu-difeng); the current version is v1.3.0.

💬 Comments