Shape the backlog first
Capture upcoming work, order it, and keep types, estimates, and owners attached before anything is committed to a Sprint.
SharklyPlan
Plan the cycle.Keep Agents on the board.
Backlog, time-boxed Sprints, Projects, and board Views live in the same Space. People commit the work. Agents execute what was planned. Progress stays visible to the team.
Used by teams at
Backlog, Sprint, Project
Planning is still a board, not a prompt
Agent execution belongs on the same plan the team already runs. If it is not on the board, it is not in the cycle.
Commit a Sprint the team can see
A Sprint is a Space time box. Pull work in, watch capacity, and keep people and Agents on the same committed set.
Group initiatives as Projects
A Project groups related Tasks across the cycle. Use it for a goal or release, not as a second tracker.
From backlog to the board
Plan, commit, and inspect without a second tool
The planning surfaces write to Tasks. Agents do not get a private plan of their own.
01Backlog
Keep uncommitted work in one place
The backlog is where upcoming Tasks wait before a Sprint. Order, type, and estimate them here so commitment is a decision, not a surprise.
- See uncommitted work without mixing it into the current Sprint
- Keep task type, priority, and estimate on each item
- Move work into a Sprint when the team is ready to commit
02Sprint
Time-box the work people and Agents share
A Sprint groups committed Tasks in a Space. Start it, watch what is in progress, and keep scope changes visible instead of burying them in chat.
- Commit a set of Tasks to a named time box
- Keep Agent-assigned work on the same Sprint board
- See progress, blockers, and leftover scope at the end of the cycle
03Project
Group the initiative, not just the week
A Project is an optional grouping for related Tasks. Use it when a goal, launch, or workstream should stay visible across Sprints.
- Attach Tasks to a Project without leaving the Space
- See related work across more than one Sprint
- Keep ownership and status on the Tasks, not on a separate doc
Screenshot pending04Views
Inspect the plan the way the team works
Saved Views keep board, list, grouping, and filters ready. Planning does not depend on rebuilding the same query every Monday.
- Board and list layouts on the same underlying Tasks
- Group by status, assignee, Project, or Sprint
- Personal or organization visibility inside the Space
Screenshot pendingThe planning system
Cycle primitives the team already expects
Backlog, Sprint, Project, and View are how the Space plans. Agents execute inside that plan.
Backlog
Uncommitted work, ordered and typed, waiting for the next cycle.
Sprint
A Space time box of committed Tasks for people and Agents.
Project
Optional grouping for an initiative, release, or workstream.
Board
The visual path through statuses the Sprint or View is tracking.
Views
Saved presets so the plan is inspectable without rebuilding filters.
Agents on the plan
Assigned Agents execute committed Tasks; they do not keep a private backlog.
Plan where the work already lives
Keep Jira or GitHub. Run the cycle here.
Synced work can still originate in another tracker. Once it is a Task, it can sit in a Sprint and be assigned to an Agent.
JiraGitHubSlack
Connected features
Planning only works if execution shares the board
Triage feeds the backlog. Agents run committed Tasks. Automations handle what repeats.
Quality of life, built in
The details that keep the cycle visible
If Agent work cannot appear on the Sprint board, it is not part of the plan.
Backlog separate from the committed Sprint
Space-scoped Sprints with a visible time box
Projects that span more than one Sprint
Board and list Views on the same Tasks
People and Agent assignees on planned work
Scope and leftover work visible at the end of the cycle
Put Agents on the same plan the team already runs
Shape the backlog, commit a Sprint, and let assigned Agents execute without leaving the board.