Jade Planner · by Nexartis
Jade Planner is the calm operating layer above Linear and GitHub: evidence-rich planning rooms, working-group memory, review queues, and reports for teams whose pace now outstrips ordinary project management.
Jade Operating Room
Linear
42 issues projects · cycles · prioritiesGitHub
18 PRs branches · checks · deploysWorking Group
Launch room mission · scope · requestsPlanning rooms
Portfolio · Launch · Ops Shared context for the conversations that decide what ships.Evidence graph
Linear + GitHub Issues, PRs, checks, branches, milestones, and provider activity in one surface.Human gates
Review first AI-speed suggestions stay calm because meaningful changes wait for approval.The Jade OS
Jade Planner is not another ticket tracker. It is where teams sense the evidence, decide the next move, review changes, and preserve the operating memory of the business.
Sense
Jade Planner reads the work systems your teams already use and turns issues, projects, pull requests, deploy signals, and milestones into planning-grade context.
Decide
Working groups collect mission, scope, cadence, roster, recommendations, and evidence so each launch, portfolio, or operating conversation has a durable home.
Review
Proposed changes are captured, explained, queued, and approved before Jade Planner updates Linear or lets automation reshape the plan.
Own
Jade Planner is a Core Cubi: configurable taxonomy, protected access, customer-specific rituals, and a production path that stays owned by the organization.
Evidence graph
The fastest teams do not need more dashboards. They need the execution evidence translated into decisions, risks, next actions, and accountable rooms.
Linear planning substrate
Projects, cycles, issues, statuses, priorities, initiatives, and planning taxonomies become the raw material for higher-level operating rooms.GitHub delivery evidence
Pull requests, branches, checks, repositories, and webhook events make delivery reality visible beside product intent.Working group memory
Groups preserve mission, scope, cadence, owners, evidence, and recommendations so AI acceleration does not erase accountability.Review queue controls
Pending sync intents, conflicts, approvals, and history keep humans in charge of when planning becomes execution-system change.Planning views
Portfolio, roadmap, Kanban, timeline, calendar, impact, and decision views are all different windows into the same connected operating context.
Operating rhythm
Authorize Linear and GitHub provider context with scoped access.
Define planning areas, working groups, ownership, cadence, and vocabulary.
Use portfolio, roadmap, Kanban, calendar, Gantt, impact, and decision views.
Approve, reject, or revisit proposed updates before they affect Linear.
Share reports and planning packages grounded in current evidence.
Who it serves
The Jade identity stays quiet and useful: clear purpose, guarded access, named decisions, and visible review before plans affect execution systems.
Turn rapid AI-assisted execution into a visible operating cadence: what matters, what changed, what is blocked, and what needs a decision.
Plan across teams, repos, launches, customers, risks, and milestones without forcing every conversation into a ticket list.
Create customer or launch rooms that preserve context, evidence, recommendations, and the next approved move.
No. Linear and GitHub remain the systems of execution. Jade Planner is the operating layer above them: planning rooms, provider evidence, working groups, reports, and review gates.
It means the product is designed around the recurring decisions of running a software business: portfolio priorities, launch readiness, dependencies, customer commitments, delivery evidence, and approved change.
It separates suggestion from authority. Evidence can arrive quickly and plans can be drafted quickly, but material updates move through review before they are sent back to execution systems.