Product case study · Live at todo.hyogomo.com

Hyogomo Project Management

A project management tool I designed and built for product and delivery teams. Tasks, QA, test cases, docs and client updates live together, and Claude can work inside it through its own MCP server.

Plan, test and ship every project from one place.

Hyogomo Project Management dashboard in the dark theme, with task counts, My Work, QA summary, upcoming tasks and team workload
  • QA handoffs
  • Waterfall Gantt
  • Test suites
  • Dependencies
  • Mind map
  • Docs
  • Client portal
  • MCP for Claude
  • Light and dark
  • Label languages
  • Android builds
  • Activity log
[ OVERVIEW / परिचय ] todo.hyogomo.com →

A personal Jira that grew into a full delivery tool: planning, QA, docs, client sharing and an AI teammate.

Role
Product manager and builder: discovery, specs, UX, code and rollout
Timeline
Feb 2026 to now, shipped in small weekly releases
Platforms
Web app, installable PWA and an Android app
Status
Live at todo.hyogomo.com
14feature areas, from QA to client links
47MCP tools Claude can use
2platforms: web and Android
5label languages, from English to Telugu
[ WHY I BUILT IT / कहानी ]
001.

The problem

Work lived in five places. Tasks in a tracker, QA rounds in WhatsApp, test cases in a spreadsheet, specs in docs and client updates in screenshots. Nobody could answer "where is this stuck?" without a call.

002.

The approach

One data model for the whole delivery loop. A dev task becomes a QA task, every round trip between QA and the developer is logged as a handoff, and docs, test runs and share links all hang off the same task IDs.

003.

The result

Every project shows its blockers, QA cycles and on-time rate on one screen. Clients get a PIN link instead of a status email, and Claude can triage, update and report on work in plain language.

[ FEATURES / सुविधाएँ ] 14 AREAS

Everything a delivery team touches, in one place

001. / Quality

QA tasks and handoffs

Work handed to QA becomes its own QA task (QA-0001) linked to the dev task. Each round trip between QA and the developer is a handoff with a verdict, notes and the build under test, so the cycle count is a fact, not a guess.

  • Queue and board views split by who holds the item
  • Fail back to Dev or Pass in one click, with a reason
  • Average cycles to pass and oldest item with QA, on the dashboard

002. / Quality

Waterfall Gantt of every cycle

The timeline draws each QA task as a waterfall: blue bars while QA holds it, amber while the developer does. Long amber bars show where work waits, and the chart exports to PNG for a weekly review.

  • Day, week and month zoom
  • Collapse by task, with a Today marker
  • Built from the handoff log, so it never needs manual updates

003. / Quality

Test cases, suites and run sheets

A test case library (TC-0001) with steps, preconditions and test data, grouped into suites. Attach a suite to a QA task and each cycle gets a run sheet: Pass, Fail, Blocked or Skip, with the actual result.

  • Filter by project, module, type, priority and status
  • Import and export to Excel
  • Run progress shown on the QA task, per cycle

004. / Planning

Task dependencies and blocked work

Link tasks as blocked by, blocks or relates to, across projects. A task with open blockers gets a Blocked badge everywhere it appears, and the drawer lists exactly what it is waiting on and where that work stands.

  • Search-and-add picker for linking
  • Cross-project blockers
  • Blocked filter in every view and over MCP

005. / Planning

Mind map of linked work

The mind map turns dependencies into clusters you can read at a glance. Red arrows are open blockers, grey ones are done, dotted lines are related work. Hover a node to trace its chain.

  • Clusters per chain of linked tasks
  • Blocked nodes outlined in red
  • Pan, zoom and fit

006. / Planning

Projects, views and delivery KPIs

Each project has an overview with on-time delivery, throughput, cycle time, lead time and aging work against a target on-time rate. Tasks open in table, board, calendar or mind map, with saved views.

  • Board grouped by status with swimlanes
  • Initiatives roll projects up into roadmap themes
  • Bulk upload and export

007. / Knowledge

Docs next to the work

Nested pages for PRDs, specs, release notes and meeting notes, linked to projects and tasks. Mention TASK-12 in a page and it links itself. Pages have owners, review status, comments and favourites.

  • Templates, full-text search and Ctrl+K page search
  • Share dialog, trash and restore
  • Export and import as Markdown

008. / Sharing

Client portal with PIN links

Share a read-only view of a project with a client. The link needs a 4-digit PIN, expires on a date you choose and can be extended, re-PINned or killed from the admin page. Every sign-in is logged.

  • Overview, work items and linked docs
  • Light and dark for the client too
  • No account needed on their side

009. / AI

An MCP server for Claude

The app ships its own MCP server. Create a personal token in Settings, add it to Claude, and Claude can list, create and update tasks, hand QA work back and forth, record test results, write docs and publish app builds, always with your role's permissions.

  • 47 tools with full field parity with the UI
  • Edits made by Claude are tagged "via Claude" in the activity log
  • Tokens can be revoked any time

010. / Trust

Activity log for every task

Every change is logged on the server, whoever made it: the web app, the Android app, a sync, a QA handoff or Claude. The task drawer shows what changed, from what to what, and who did it.

  • Logged on the backend, so no source can skip it
  • QA handoffs show on the dev task too
  • Comments sit in the same timeline

011. / Craft

Light, dark and system themes

The whole app follows the hyogomo.com look: black and grey, one red accent, DM Sans and square corners. Pick Light, Dark or System in Settings or from the sidebar.

  • Dark by default
  • Same look on the client portal and sign-in page
  • Saved per browser

012. / Craft

Label languages

Section labels can carry a second language next to English, like [ WORKSPACE / कार्यक्षेत्र ]. Choose None, Hindi, Kannada, Tamil or Telugu. It is a small touch that makes the tool feel local.

  • English only by default
  • Applies to sidebar and page eyebrows
  • One setting, saved per browser

013. / Mobile

Android app and build sharing

An Android app for updates on the move. Admins publish a new build from the Admin page, by upload or from an EAS link, and everyone sees the latest version with its release notes in Settings.

  • Signed download links that expire in 24 hours
  • Release notes and download counts per build
  • Installable PWA for the web app as well

014. / Reporting

Initiatives and analytics

Initiatives group projects under a roadmap theme with an owner, target date and progress. Analytics shows a timeline of every task against its dates, so overdue work stands out.

  • At-risk initiatives flagged in red
  • Shareable with teammates
  • Change history per initiative
[ HOW IT IS BUILT / निर्माण ]

Small releases, shipped weekly

Stack

  • Vanilla JS + Vite
  • Tailwind
  • Node.js + Express
  • MongoDB + GridFS
  • Serverless-style handlers
  • Expo / React Native
  • MCP (Streamable HTTP)
  • GitHub Actions → VPS

Every merge to the main branch runs the tests and deploys to my own server through GitHub Actions. Claude pairs on the code, and the same MCP server it uses to build the app lets it manage the work inside it.

  1. Oct 2026

    QA section: QA tasks, handoff cycles, waterfall Gantt and test cases

  2. Oct 2026

    MCP server so Claude can manage work with a personal token

  3. Nov 2026

    Dependencies, mind map, Docs upgrade and light/dark themes

  4. Nov 2026

    Client portal, profile photos and the hyogomo.com restyle

  5. Nov 2026

    Server-side activity log, Android build sharing and the rebrand

[ TRY IT / देखें ]

Want a tool like this for your team?

The app is invite only. Open it if you have an account, or tell me about your team and I will walk you through it.