TukTak Technology logo

Delivery Roadmap

The GitHub board, checked against the Requirements Analysis, with decision gates and a timeline
Docs › Roadmap · Requirements · Data flow · Database

Every task maps back to a requirement section (§4) and to the decisions it depends on (D13), linked straight to the decision tracker. A phase can only start building once its decision gate is clear.

The phases and task IDs are the ones on your GitHub board (checked 2026-11-14). Tasks I added on 14 Nov are marked Added, deleted duplicates Duplicate removed, and tasks better done in another phase Move suggested. Durations are planning estimates, not commitments.

8Phases on the board (P0–P7)
64Original tasks (3 duplicates removed)
+11Tasks added to the board from the requirements
~18 wksKickoff to pilot (estimate)
48Original tasks waiting on an open decision
42Open decisions on the build path
Critical path: the build can't start on the money flow (P5) until legal confirms escrow (D24) and the VAT consultant answers (D29). Both are external and slow, so request them in week 1. Founders can close the rest in one or two sessions: D24 D29 D28 D43 D44 D23 D11 D12 D13 D14 D17

Board check

What I found on 14 Nov comparing the board with the requirements; all of it has been applied on the board (fields, statuses, views, automations, added and removed cards). See Card workflow.

Before: 75 items, all in Todo → After: 82 cards (75 MVP + 7 Later), 47 Needs decision · 11 Ready · 24 BacklogOpen the board ↗
DuplicatesP1.7, P1.8 and P5.4 each appear twice (3 extra cards). The board shows 75 items; after removing them it has 8 phase cards + 64 unique tasks.
Phases are cards, not a fieldThe 8 "Phase N" items sit in Todo next to the tasks, and tasks belong to a phase only through the title prefix. Add a Phase single-select field and archive or pin the phase cards.
Everything is in TodoAll 75 items are Todo. The board already has Needs decision / Ready columns; 48 of the 64 tasks depend on a decision that is still open and belong in Needs decision.
No details on cardsEvery card I opened (40 of 75; GitHub rate-limited the rest) has an empty description, no assignee, size, dates or labels. Only P0.4 names its decisions.
Ordering clashesP4.4 (15-min payment window) needs P5.2 callbacks; P4.7 cancellations need P5.6 fees; NID is collected in P2 but encrypted in P7.1. Merge or link these.
Missing from the boardSSLCommerz merchant application, trade licence/BIN, domains, SMS gateway, NID OCR, payment method at posting, "ready mode", payout disbursement, Play Store release, pilot marketing, testimonials, and the §16 future list.
What's already good: decisions first (P0), payments explicitly decision-gated, an auditable ledger with reconciliation, admin action logs, and a limited pilot with fix-before-expand. The phase order matches the requirements' system flow.

Timeline

Click a phase to jump to its tasks.

Phase
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
P0 MVP scope and decisions12 tasks · 32 open decisions
W1–2
P1 Product and technical foundations10 tasks · 5 open decisions
W2–4
P2 Accounts and verification10 tasks · 9 open decisions
W4–7
P3 Categories and task posting8 tasks · 7 open decisions
W6–9
P4 Search, bidding, and task execution10 tasks · 11 open decisions
W8–12
P5 Payments, escrow, and payouts (decision gated)10 tasks · 13 open decisions
W9–14
P6 Disputes, billing, and admin8 tasks · 5 open decisions
W12–16
P7 Security, launch readiness, and pilot10 tasks · 6 open decisions
W15–18
Later After MVP (§16)7 tasks · 3 open decisions
W19–22

Week numbers are counted from kickoff. Phases overlap on purpose: backend for the next phase starts while the current one is in QA. Estimated for 3 developers (backend, web, Android) plus the founders; total effort is about 250 developer-days, so with 2 developers expect about 25 weeks.

Decision gates

Decisions that must be settled before a phase is built. Click a code to open it in the tracker.

DecidedPartly decidedProposal waitingNeeds expertNot discussed

P0 · MVP scope and decisions32 to close

  • D01 Seeker NID rule can't be checkedProposal waiting
  • D03 Password policy: “standard” vs “strong”Proposal waiting
  • D04 OTP expiry and retry limitsProposal waiting
  • D05 Business account fieldsProposal waiting
  • D06 Seeker DOB and gender stored but not requiredProposal waiting
  • D07 Rejected TukTaker flowProposal waiting
  • D08 Work location: one vs manyProposal waiting
  • D11 Payment method chosen at postingProposal waiting
  • D14 Escrow auto-releaseProposal waiting
  • D17 “I have arrived” can be abusedProposal waiting
  • D18 “Confirm payment received” stepProposal waiting
  • D19 No-show handlingProposal waiting
  • D20 Chat and off-platform dealsProposal waiting
  • D21 “Set app to ready mode”Not discussed
  • D22 Redemption cap periodProposal waiting
  • D23 Payout destinationsProposal waiting
  • D24 Legal check on holding moneyNeeds expert
  • D25 Gateway fees and “tip fees”Proposal waiting
  • D26 Failed or double paymentsProposal waiting
  • D28 Commission: 20/18/16 vs 17/15/13Proposal waiting
  • D29 Who bears VAT, and on whatNeeds expert
  • D30 TukTaker 2-hour cancellation window and penaltyProposal waiting
  • D31 Seeker cancellation fees vs payment timingProposal waiting
  • D32 Unpaid penaltiesProposal waiting
  • D33 Who pays the 5% refund admin feeProposal waiting
  • D34 Refund approvals, disputes, credit limitsPartly decided
  • D35 “Mandatory” ratings can't be forcedProposal waiting
  • D40 NID hash can be reversedProposal waiting
  • D42 Hotline, hours, slogan, emergency engagementNot discussed
  • D43 MVP scope cutProposal waiting
  • D44 Non-functional requirements missingProposal waiting
  • D45 Safety featuresProposal waiting

P1 · Product and technical foundations5 to close

  • D16 Task, bid, assignment, escrow and payout statusesDecided
  • D37 Admin spec and rolesProposal waiting
  • D38 Retention: profiles forever, NID imagesProposal waiting
  • D39 Backups can't stay TBCProposal waiting
  • D40 NID hash can be reversedProposal waiting
  • D44 Non-functional requirements missingProposal waiting

P2 · Accounts and verification9 to close

  • D01 Seeker NID rule can't be checkedProposal waiting
  • D02 One mobile number for both roles?Decided
  • D03 Password policy: “standard” vs “strong”Proposal waiting
  • D04 OTP expiry and retry limitsProposal waiting
  • D05 Business account fieldsProposal waiting
  • D06 Seeker DOB and gender stored but not requiredProposal waiting
  • D07 Rejected TukTaker flowProposal waiting
  • D08 Work location: one vs manyProposal waiting
  • D40 NID hash can be reversedProposal waiting
  • D44 Non-functional requirements missingProposal waiting

P3 · Categories and task posting7 to close

  • D09 Pet question has no “No pets” optionProposal waiting
  • D10 “All steps mandatory” vs “photo where applicable”Proposal waiting
  • D11 Payment method chosen at postingProposal waiting
  • D12 When does bidding close?Partly decided
  • D13 Budget, counter-offers, editing bids and tasksProposal waiting
  • D16 Task, bid, assignment, escrow and payout statusesDecided
  • D31 Seeker cancellation fees vs payment timingProposal waiting
  • D43 MVP scope cutProposal waiting

P4 · Search, bidding, and task execution11 to close

  • D08 Work location: one vs manyProposal waiting
  • D13 Budget, counter-offers, editing bids and tasksProposal waiting
  • D15 Payment timeout after a bid is acceptedDecided
  • D17 “I have arrived” can be abusedProposal waiting
  • D18 “Confirm payment received” stepProposal waiting
  • D19 No-show handlingProposal waiting
  • D20 Chat and off-platform dealsProposal waiting
  • D21 “Set app to ready mode”Not discussed
  • D30 TukTaker 2-hour cancellation window and penaltyProposal waiting
  • D31 Seeker cancellation fees vs payment timingProposal waiting
  • D35 “Mandatory” ratings can't be forcedProposal waiting
  • D44 Non-functional requirements missingProposal waiting

P5 · Payments, escrow, and payouts (decision gated)13 to close

  • D11 Payment method chosen at postingProposal waiting
  • D14 Escrow auto-releaseProposal waiting
  • D15 Payment timeout after a bid is acceptedDecided
  • D22 Redemption cap periodProposal waiting
  • D23 Payout destinationsProposal waiting
  • D24 Legal check on holding moneyNeeds expert
  • D25 Gateway fees and “tip fees”Proposal waiting
  • D26 Failed or double paymentsProposal waiting
  • D27 Stored balances duplicate the ledgerProposal waiting
  • D28 Commission: 20/18/16 vs 17/15/13Proposal waiting
  • D29 Who bears VAT, and on whatNeeds expert
  • D32 Unpaid penaltiesProposal waiting
  • D33 Who pays the 5% refund admin feeProposal waiting
  • D34 Refund approvals, disputes, credit limitsPartly decided

P6 · Disputes, billing, and admin5 to close

  • D29 Who bears VAT, and on whatNeeds expert
  • D33 Who pays the 5% refund admin feeProposal waiting
  • D34 Refund approvals, disputes, credit limitsPartly decided
  • D36 Invoice period and TukTaker invoice contentNot discussed
  • D37 Admin spec and rolesProposal waiting

P7 · Security, launch readiness, and pilot6 to close

  • D38 Retention: profiles forever, NID imagesProposal waiting
  • D39 Backups can't stay TBCProposal waiting
  • D40 NID hash can be reversedProposal waiting
  • D41 Blank disclaimer rowsNot discussed
  • D42 Hotline, hours, slogan, emergency engagementNot discussed
  • D45 Safety featuresProposal waiting

Later · After MVP (§16)3 to close

  • D28 Commission: 20/18/16 vs 17/15/13Proposal waiting
  • D43 MVP scope cutProposal waiting
  • D44 Non-functional requirements missingProposal waiting

Requirements coverage

How many tasks cover each section of the requirements analysis, by phase. No section is left without a task.

Requirement sectionP0P1P2P3P4P5P6P7LaterTotal
§0 System flow341210
§1 Seeker account235
§2 TukTaker account218112
§3 Categories1214
§4 Task posting1629
§5 Bidding & execution111710
§6 Payments, escrow, payouts3111915
§7 Commission & VAT2114
§8 Cancellation11215
§9 Refunds & disputes1236
§10 Ratings1113
§11 Invoicing & billing22
§12 Admin & reports2111510
§13 Security & retention22111411
§14 Legal & compliance213
§15 Operations & brand246
§16 Future scope167

Phases & tasks

Size: S ≤ 2 days · M 3–5 days · L 1–2 weeks. Owner is the main discipline; most tasks also need web or app work.

Download CSV
P0

MVP scope and decisions

Weeks 1–2
GoalClose the decisions that block building and start the slow external paperwork.
Done whenEvery decision gating P2-P5 is decided; acceptance criteria written; merchant account applied for.
IDTaskReq.OwnerSizeBlocked by
P0.1Review the 45-item decision tracker and assign owners and dates§0BIZS—
P0.2Confirm MVP categories and user flows; separate future scope§3 §16BIZSD43
P0.3Resolve payment, escrow, payout, commission, VAT, cancellation, refund, and dispute rules
Biggest card on the board: 12 decisions. Split per topic so progress is visible.
§6 §7 §8 §9BIZMD11 D14 D22 D23 D25 D26 D28 D30 D31 D32 D33 D34
P0.4Get expert sign-off on customer-fund custody and VAT treatment (D24, D29)
Long lead time: start day 1.
§6 §7 §14BIZMD24 D29
P0.5Decide account and identity rules: Seeker NID, password, OTP, TukTaker verification and rejection§1 §2BIZSD01 D03 D04 D05 D06 D07 D08 D40
P0.6Decide operational rules: chat, arrival verification, no-shows, ratings, support hours, and safety§5 §10 §15BIZSD17 D18 D19 D20 D21 D35 D42 D45
P0.7Update requirements and database design to match approved decisions§0BEM—
P0.8Write acceptance criteria for MVP flows§0BIZM—
P0.9AddedApply for SSLCommerz merchant account and the payout/disbursement account
Weeks of lead time; P5 can't go live without it.
§6BIZMD23 D24
P0.10AddedTrade licence, VAT/BIN registration
Required by §14 and for invoices.
§14BIZM—
P0.11AddedRegister TukTakKaj.com (+ TukiTakiKaj.com redirect, .com.bd) and info/admin/feedback emails§15OPSS—
P0.12AddedChoose SMS gateway (OTP) and push-notification provider
P2.1 depends on it.
§1 §2OPSSD04 D44
P1

Product and technical foundations

Weeks 2–4
GoalJourneys, screens, platform targets and the technical skeleton are agreed.
Done whenScreens approved; data model and status machine signed off; dev/staging/prod deploy from CI.
IDTaskReq.OwnerSizeBlocked by
P1.1Map Seeker and TukTaker journeys, including errors and recovery§0FEM—
P1.2Sketch sign-up, task posting, bidding, execution, payment, payout, and support screens
UI Prototypes A/B/C already cover most screens: pick one and fill gaps.
§0FEM—
P1.3Confirm platforms, languages, notifications, accessibility, and service targets§0BIZSD44
P1.4Define roles and permissions for users, operations/support, finance, and super admins§12BESD37
P1.5Set up repository workflow, environments, deployment, and monitoring
Include the midnight deploy window from §12.
§12OPSM—
P1.6Define core data model and status transitions for users, tasks, bids, assignments, payments, and payouts
Mostly done in the database dictionary (D16 decided).
§0 §4 §5 §6BEMD16
P1.7Define security and privacy controls for NID data, access logs, retention, and deletion§2 §13BESD38 D40
P1.8Define backup and restore requirements§13OPSSD39
P1.7Duplicate removedDefine security and privacy controls for NID data, access logs, retention, and deletion
Duplicate card: delete one.
§2 §13BES—
P1.8Duplicate removedDefine backup and restore requirements
Duplicate card: delete one.
§13OPSS—
P2

Accounts and verification

Weeks 4–7
GoalSeekers and TukTakers sign up and manage profiles; admins verify TukTakers.
Done whenSeeker registers with OTP; TukTaker submits NID + selfie and is approved or rejected with a reason.
IDTaskReq.OwnerSizeBlocked by
P2.1Implement mobile sign-up and OTP verification§1 §2BEMD02 D04
P2.2Add password creation, reset, and change flows§1 §13BESD03
P2.3Build Seeker profiles and profile editing
Personal vs Business account type (D05) not named on the board.
§1FEMD01 D05 D06
P2.4Build TukTaker registration and document submission
Spell out: 18+ gate, DOB check, NID front/back, app-directed selfie, work location.
§2APPLD08
P2.5Add the admin verification queue, approve/reject actions, and rejection reasons§2 §12ADMMD07
P2.6Add resubmission and re-verification rules§2APPSD07
P2.7Send verification and account-status notifications§2BESD44
P2.8Restrict task browsing and bidding to verified TukTakers§2 §5BES—
P2.9AddedAuto-fill name and DOB from the NID image (OCR), manual fallback
Required by §2, not on the board.
§2BEM—
P2.10AddedEncrypt NID data from the first upload (bring P7.1 forward)
NID is collected in P2, so encryption can't wait for P7.
§2 §13BEMD40
P3

Categories and task posting

Weeks 6–9
GoalSeekers post complete tasks; the bidding clock runs.
Done whenA task in each MVP category can be posted, edited, published, cancelled and expires on schedule.
IDTaskReq.OwnerSizeBlocked by
P3.1Configure MVP categories and subcategories§3BESD43
P3.2Build task creation for description, schedule, location, and budget§4FELD10
P3.3Add category-specific fields, including delivery pickup/drop-off details where needed
Delivery also needs an 18+ TukTaker rule.
§3FES—
P3.4Add pet and photo questions according to approved decisions§4FESD09 D10
P3.5Add task summary, edit, publish, and cancellation flows§4 §8FEMD13 D31
P3.6Implement bidding close time and task status rules§4BEMD12 D16
P3.7Let Seekers view and manage posted tasks§4FEM—
P3.8AddedPayment method choice at posting (bKash / Nagad / Bangla QR) or at acceptance
Listed in §4 steps; missing on the board.
§4 §6FESD11
P4

Search, bidding, and task execution

Weeks 8–12
GoalVerified TukTakers find tasks, bid and do the job; both sides rate.
Done whenStaging: post → 3 bids → counter → accept → pay → arrive → complete → rate.
IDTaskReq.OwnerSizeBlocked by
P4.1Search tasks using TukTaker work locations and approved filters
Add keyword search for the "Other" category (§3).
§5 §3APPLD08
P4.2Let TukTakers submit, edit, and withdraw bids under agreed rules§5APPMD13
P4.3Let Seekers review bids and negotiate within agreed limits§4 §5FEMD13
P4.4Implement bid acceptance and the 15-minute payment window
Overlaps P5.2 (also "15-minute timeout") and needs payment callbacks from P5: merge or link.
§4 §6BEMD15
P4.5Notify both sides about assignment and task updates§0BEMD44
P4.6Add arrival reporting and the approved verification mechanism§5 §8APPMD17
P4.7Implement task completion, no-show, and cancellation flows
Fees and penalties are calculated in P5.6: depends on it.
§5 §8BELD18 D19 D30 D31
P4.8Add in-app chat if it remains in the MVP§5 §13BELD20
P4.9Add mutual ratings and reminders§10APPMD35
P4.10AddedDefine or drop "Set app to ready mode"
In the requirements with no description; not on the board.
§5 §12BIZSD21
P5

Payments, escrow, and payouts (decision gated)

Weeks 9–14
GoalMoney moves safely: pay into escrow, release, commission + VAT, payout.
Done whenSandbox money loop: pay ৳1,400 → release → wallet credited net of commission/VAT → payout to a bKash test number; reconciliation balances.
IDTaskReq.OwnerSizeBlocked by
P5.1Move suggestedConfirm the provider supports approved pay-in, escrow, refunds, and payouts
Do this in P0 with P0.9: it decides the whole phase.
§6BIZSD23 D24
P5.2Implement payment initiation, callbacks, and the 15-minute timeout§6BELD11 D15
P5.3Record every money movement in an auditable ledger§6 §13BELD27
P5.4Implement escrow release, dispute holds, and auto-release if approved§6 §9BEMD14 D34
P5.4Duplicate removedImplement escrow release, dispute holds, and auto-release if approved
Duplicate card: delete one.
§6 §9BEM—
P5.5Handle failed and duplicate payments safely§6BEMD26
P5.6Calculate approved commission, VAT, tips, cancellations, refunds, and credits§6 §7 §8 §9BELD25 D28 D29 D32 D33
P5.7Let TukTakers request payouts and track payout status
Add the rules: ৳500–10,000, ৳5 fee, cap period.
§6APPMD22 D23
P5.8Add reconciliation and balance checks§6BEMD26
P5.9AddedPayout approval and disbursement to bKash / Nagad / Bangla QR
P5.7 covers the request; nothing covers actually sending the money.
§6 §12BEMD23
P6

Disputes, billing, and admin

Weeks 12–16
GoalOps runs the platform without database access; users see what they paid and earned.
Done whenAdmin can verify, refund, credit, approve payouts and pull the 4 reports; invoices generate.
IDTaskReq.OwnerSizeBlocked by
P6.1Let users submit disputes and evidence§9FEMD34
P6.2Build admin review, approval, refund, and goodwill-credit workflows§9 §12ADMLD33 D34
P6.3Add a second approval step if required by final policy§9 §12ADMSD34
P6.4Add billing history and transaction views§11FEM—
P6.5Provide Seeker and TukTaker statements/invoices under approved tax rules
Include the ৳20 invoice charge.
§11BEMD29 D36
P6.6Build admin dashboards for users, tasks, KYC, disputes, refunds, credits, and payouts§12ADMLD37
P6.7Add user, revenue, task, and VAT reports§12ADMMD29
P6.8Enforce admin action logs and role-based access§12 §13BEMD37
P7

Security, launch readiness, and pilot

Weeks 15–18
GoalLegal, safety and operations ready; limited pilot in Chattogram.
Done whenApp and web live, pilot users onboarded, hotline staffed, pilot blockers fixed.
IDTaskReq.OwnerSizeBlocked by
P7.1Move suggestedEncrypt NID data and use safe duplicate checking
Move to P2 (see P2.10); keep the duplicate check here.
§2 §13BEMD40
P7.2Enforce data retention and deletion schedules§13BEMD38
P7.3Configure backups and rehearse restoration§13OPSSD39
P7.4Review access controls, rate limits, audit logs, and payment failure handling§13BEM—
P7.5Test full Seeker and TukTaker journeys with realistic scenarios§0QAM—
P7.6Prepare support procedures, hotline, emergency guidance, and user-facing terms
Fill the 14 blank disclaimer rows (D41).
§14 §15BIZMD41 D42 D45
P7.7Run a limited pilot and track completion, cancellation, dispute, payment, and payout issues§15BIZM—
P7.8Fix pilot blockers before expanding§0BEM—
P7.9AddedPlay Store release and web launch on TukTakKaj.com§15APPS—
P7.10AddedPilot marketing (halal ad rules), Metro ads, collect testimonials
§10 testimonials and §15 marketing aren't on the board.
§10 §15BIZM—
Later

After MVP (§16)

Weeks 19–22
GoalParked items from section 16; start only after the pilot shows traction.
Done whenPrioritised from pilot data.
IDTaskReq.OwnerSizeBlocked by
L.1AddediOS app§16APPLD44
L.2AddedCommission tiers Silver / Gold / Platinum§7BEMD28
L.3AddedDebit/credit cards§16BEM—
L.4AddedFingerprint collection for TukTakers§16APPM—
L.5AddedConnection fee for Seekers, special offers, value-added charges§16BEM—
L.6AddedExtra categories (car rental, driver, maid, nursing...) after compliance review§16BIZMD43
L.7AddedEmergency PCA service with hotline, training and certification§16BIZL—

Card workflow

How a card moves on the board. Replaces the current Todo / In Progress / Done set.

Backlog→Needs decision→Ready→In progress→In review→Testing→Done

A card can only go back one step (e.g. Testing → In progress when a bug is found). Needs decision is a parking spot: a card leaves it straight to Ready once its D-items are closed.

StatusMeaningEnter whenLeave when
BacklogCaptured but not refined. New cards land here.Anyone adds a card with the template.Description filled, Phase + Size set, decisions listed.
Needs decisionWaiting on a founder, legal, VAT or provider decision (D-numbers in the Decisions field).Any open D-item in Decisions.Every listed decision is Decided in the tracker.
ReadyDefinition of Ready met; can be picked up next.Acceptance criteria written, decisions closed, dependencies done, sized.Someone assigns themselves and starts.
In progressBeing built. Limit: 2 cards per person.Assignee set, branch created.PR opened and linked to the card.
In reviewCode review and product review.PR linked; self-checked against acceptance criteria.PR approved and merged to the staging branch.
TestingVerified on staging against the acceptance criteria.Deployed to staging.QA or the requester signs off; bugs become new cards.
DoneMeets the Definition of Done. Auto-archived after 14 days.Acceptance criteria pass on staging, docs updated.—
Definition of Ready
  • Template filled, acceptance criteria testable
  • No open decisions in the Decisions field
  • Depends-on cards are Done
  • Phase, Size, Priority, Area set; L or smaller
Definition of Done
  • All acceptance criteria pass on staging
  • Code reviewed and merged; tests added for money and status logic
  • Docs updated if a rule changed (requirements, database dictionary)
  • No open bugs from Testing

Fields

FieldTypeValuesWhy
PhaseSingle selectP0 … P7, LaterReplaces the 8 phase cards; group the table and roadmap by it.
SizeSingle selectS (≤2 days) · M (3–5 days) · L (1–2 weeks)Anything bigger than L gets split.
PrioritySingle selectMust · Should · CouldMust = MVP launch blocker.
AreaSingle selectFounders · Backend · Web · Android · Admin · DevOps · QAMain discipline; filter your own work.
DecisionsTexte.g. D13 D31Open D-items from the tracker. Empty = not blocked.
ReqTexte.g. §4 §8Requirement sections the card delivers.
SprintIteration2 weeksPlan and review in sprints; powers the roadmap view.
Views
  • Board: Board grouped by Status, Later phase hidden (Daily stand-up)
  • Plan by phase: Table grouped by Phase, sorted by Priority (Planning and the founders' overview)
  • Roadmap: Roadmap by Sprint, grouped by Phase (Timeline and dates)
  • Decisions: Table filtered to Status = Needs decision, showing Decisions (Weekly founders' decision meeting)
  • My work: Board filtered to assignee = me (Each person's own queue)
Automations (built-in workflows)
  • Item added to project → Backlog
  • Pull request linked to issue → In review
  • Code changes requested → In progress
  • Code review approved → stays In review
  • Pull request merged → Testing
  • Item reopened → In progress
  • Item closed → Done; Status set to Done → issue auto-closed
  • Auto-archive closed items after 14 days
Card template
**Goal** – one sentence, user-facing outcome
**Requirement** – §N link to requirements_analysis.html
**Decisions** – D-numbers this depends on (or "none")
**Acceptance criteria**
- [ ] Given … when … then …
- [ ] Error / edge case …
**Out of scope** – what this card does not do
**Depends on** – other card IDs
Rhythm
  • Monday · 30 min: Founders' decision meeting on the Decisions view: close D-items and move cards to Ready.
  • Daily · 10 min: Stand-up on the Board view: what moved, what's stuck, respect the WIP limit.
  • Every 2 weeks: Sprint planning: pull Ready cards by Priority into the next Sprint. Demo what reached Done.