Curva ✕ Pasukuru — LINE-native Ecommerce Plan
Detailed multi-phase plan + framework. Read in order.
Files
| # | File | Purpose | Status |
|---|---|---|---|
| 0 | 00-master-plan.md | Top-level rollup, phase summary, glossary | ✅ |
| 1 | 01-framework.md | Planning methodology, item template, DoR/DoD | ✅ |
| 2 | 02-phase-0-foundation.md | Phase 0 — webhook completion (10 items) | ✅ |
| 3 | 03-phase-1-liff-wrap.md | Phase 1 — LIFF wrap (12 items) | ✅ |
| 4 | 04-phase-2-ux-glue.md | Phase 2 — UX glue (8 items) | ✅ |
| 5 | 05-phase-3-payment-agent.md | Phase 3 — payment + agent (7 items) | ✅ |
| 6 | 06-phase-4-multishop.md | Phase 4 — multi-shop (OPTIONAL, deferred) | ✅ |
| 7 | 07-cross-cutting.md | Infra, ops, manual tasks (8 items) | ✅ |
| 8 | 08-test-strategy.md | Test gates per phase | ✅ |
| 9 | 09-risk-register.md | 16 risks tracked + kill switches | ✅ |
| 10 | 10-jira-tickets.md | Pre-drafted tickets, file order | ✅ |
Executive summary
| Phase | Scope | CC sessions | Calendar (parallel) | MVP? |
|---|---|---|---|---|
| 0 | Foundation: webhook v1 + identity column | 6 | 1 day | ✅ MVP |
| 1 | LIFF wrap: Pasukuru FE inside LINE | 9 | 1-2 days | ✅ MVP |
| 2 | UX glue: Flex picker, RichMenu, Scenarios | 8 | 1-2 days | partial MVP |
| 3 | Payment + agent + polish | 9 | 2 days | post-MVP |
| 4 | Multi-shop (optional) | 3 | 1 day | DEFER |
| X | Cross-cutting infra/tests | 7 | 2 days | always |
Total to ship: ~39 CC sessions = 8-10 days parallel (sub-agent worktrees) or 15-20 days serial.
MVP cutline: Phase 0 + Phase 1 + Phase 2 items {C5, C7} = ~18 sessions = 4-5 days parallel.
Approval gates
Before starting:
- User approves master plan
- User decides 0.D-1 (HMAC algo + rotation)
- User decides 0.D-2 (line_user_id uniqueness scope)
- User decides 1.D-1 (multi-tenant LIFF routing)
- User decides 1.D-3 (cookie/token strategy)
- User decides 3.D-2 (LINE Pay in MVP?)
Phase 0 unblocked once approved + decisions 0.D-* resolved.
How to use this plan
- Read 00-master-plan.md for orientation
- Read 01-framework.md for methodology (item template, DoR/DoD)
- For execution: open the current phase doc, find an item with status=Ready, follow item template
- Update tracking matrix as items move through Backlog → Ready → InProgress → Review → Done
- Update vault log + memory after each phase exit
Update protocol
This plan evolves. Update rules:
- After each phase exit → re-estimate remaining phases based on actuals
- After each decision → mark in phase doc + risk register
- After each incident → add to risk register
- Bump
last-edited-by+datefront-matter on every edit - Append to vault
log.mdper global rule