Project managementCAN I VIBECODE
Shortcut?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Shortcut (formerly Clubhouse) is a product-development project management tool uniting issue tracking, sprints, roadmaps, and goals. Core hierarchy: Stories (shippable customer value with requirements/acceptance criteria), Sub-tasks (implementation steps tied to GitHub), Epics (cross-functional projects composed of Stories), and Objectives (strategic goals with Key Results linking Epics to company metrics). Workflows are customizable with states, WIP limits, estimate scales, labels, custom fields, and story templates. Iterations (time-boxed sprints) display burndown and cumulative flow reports. Roadmap view organizes Epics by team with health statuses (On Track/Off Track/At Risk) and export. Automation, Slack create/update, GitHub/GitLab/Bitbucket branch and PR linking, and data importers from other PM tools are built in. Includes Docs for in-tool documentation and Kanban boards for back
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for Shortcut's core product-development workflow: story-centric issue tracking organized under Epics and Objectives. Workflow: create Stories (title, description, acceptance criteria, owner, due date, estimate, labels, custom fields, dependencies/blockers); break Stories into Sub-tasks; group Stories into Epics; group Epics into Objectives with Key Results; move Stories through custom workflow states (e.g. Backlog, In Progress, In Review, Done) with WIP limits; plan time-boxed Iterations (sprints); track progress via burndown and cumulative flow charts; publish a team-based Roadmap view with per-Epic health status (On Track/Off Track/At Risk). User-facing requirements: Kanban board with drag-and-drop state changes; Story detail drawer with comments and activity history; iteration planning page with backlog swimlane; roadmap timeline; story templates; search/filters by assignee, label, custom field; notifications. Technical requirements: React + TypeScript SPA; Node/Postgres API (REST); real-time updates via WebSockets; auth with admin/member/viewer roles; seed demo data; CSV/JSON import. Implementation approaches: Postgres schema for stories, sub_tasks, epics, objectives, iterations, custom_workflow_states; cached rollups for Epic/Objective progress percentages; event-sourced activity log. Do not copy Shortcut's brand name, logo, marketing copy, or visual design; avoid reproducing their exact layout, color palette, or proprietary UI chrome—use generic labels (Stories, Epics, Objectives) without mimicking their interface. Deliberate out-of-scope: GitHub/GitLab/Bitbucket integrations, Slack integration, docs/wiki module, importers from other PM tools, mobile apps, public API for third-party consumers, billing/SSO admin, and legacy Project-level grouping (use only Epics). Deliver a README covering local setup (dev, migrations, seed), architecture overview, API endpoints, and important limitations (single-tenant, no production auth hardening, no third-party integrations, minimal test coverage).