Opinionated planning, native to GitHub.

Fisk 0.1.0 / For Mac

Fisk is a native Mac app for planning on GitHub. Work moves through three phases, and only once it's defined. Everything is stored there as issues, comments and Project fields, with AI skills you can rewrite at every step.

Download for Mac
Fig. 1 / The fish22 × 13 cells, #111111 on white

01 / Process

Three phases. Three questions.

Each phase answers one question, and work only moves on once it's defined. Follow one idea down: planning draws the shape, building fills it in, and a release sends it out.

01

Capture

Is this worth doing?

Anything can be an idea: a note, a call, a Slack thread. Evidence collects as comments until it's framed.

01CapturedIdea / New
GateNothing. Anything can be an idea.
Fisk⌃⌥Y catches it from any app.capturefind-similar
GitHubAn issue labeled idea
02FramedIdea / Framing
GateThe problem is written.
FiskEvidence collects as comments.flesh-outchallenge
GitHubComments on that issue
02

Plan

Is it ready, and what comes first?

A spec says what to build and why. Specs share one rank, and a ready one starts when there's room.

03DraftedSpec / Drafting
GateA size and an owner. Never an XL.
FiskPromote makes the spec from its idea.write-spec
GitHubA sub-issue labeled spec
04ReadySpec / Ready
GateEvery section is written, and it has at least one task.
FiskFill in drafts whatever the gate says is missing.validate-specbreak-into-tasks
GitHubTasks as sub-issues, and a Rank
03

Build

Is it on track?

The spec's tasks move across a board. Its owner posts an update every week, and finished work goes out in the next release.

05BuildingTask / In progress
GateAn owner. Going over capacity warns you.
FiskBuild opens the task in Claude Code.buildweekly-update
GitHubStatus, owner and Start date
06In reviewTask / Review
GateA pull request that closes the task.
FiskA fresh session tests each criterion.review
GitHubA pull request
07ReleasedRelease
GateEvery acceptance criterion checked, and the pull request merged.
FiskThe Roadmap shows each spec through to its release.
GitHubA milestone and its release

02 / Method

Opinionated about definition. Flexible about cadence.

The method comes from Shape Up and kanban: shape the work, size it, and pull it when there's room. If your team plans in cycles or runs Scrum sprints, turn on iterations.

Definition first.

An idea needs its problem. A spec needs its solution, its risks and what's out of scope. A task needs acceptance criteria. Nothing moves without them.

Flow by default.

Specs share one rank, and a ready spec starts when there's room under the capacity.

Iterations when you want them.

For teams that start and stop together, in cycles or sprints. An iteration is a GitHub field, a column and a filter.

Releases, not dates.

A release goes out every two weeks, and a spec is planned for the one it ships in.

Size before scope.

In calendar weeks
XS
Under 1
SM
Under 2
MD
Under 4
LG
Under 6
XL
Over 6. Never a spec: split it first.

Work over a week needs a spec. Smaller tasks and bugs go straight on the board.

03 / AI

AI at every step. You make the calls.

Skills capture, draft, challenge, build and review. In the app every change is a proposal you apply, and nothing moves through a gate without your yes.

Skills

A skill is instructions your team wrote for one kind of job, kept as a file in your repo. Edit the starters or write your own.

MCP

Ten tools let Claude Code read and change the plan from a checkout, under the same gates as the app.

Your tools

Fisk picks up what's on your Mac: Claude Code, your checkouts and the MCPs connected there. Build opens a task in the tool you choose.

Your account

It runs on your own Claude and your own GitHub, so client work stays with the client.

The eleven starters
captureA note, call or thread becomes an idea
find-similarHas this been captured already?
groom-captureFind duplicate and stale ideas
flesh-outRough notes into a clear description
challengePoke holes before it moves on
write-specA spec from an idea
validate-specIs the spec ready to build?
break-into-tasksA ready spec into tasks
buildBuild a task, or the next ready one
reviewTest each acceptance criterion
weekly-updateThe week's status, drafted for the owner

04 / GitHub

If Fisk went away, the record would still be complete.

Stored

Ideas, specs, tasks and bugs are GitHub issues. Status, size and rank are Project fields. A release is a milestone.

Synced

A change in Fisk is written to GitHub straight away, and Fisk re-reads GitHub every five minutes.

Team

Teammates work in GitHub and don't need Fisk. They see the same issues, boards and fields.

Native

A Mac app that uses the GitHub CLI you're already signed in to. No server, no new account.

The pieces

Setup makes the settings on GitHub and opens one pull request with every file, for you to review.

Labelsidea, spec, task, bug and needs-triage
Issue formsOne for each kind of issue
TemplatesPull requests and release notes
ProjectStatus, Size, Health, Rank and Start date
Board viewsCapture, Plan and Build
SkillsThe starters, as files in the repo
Agent fileThe process, written for coding agents
PluginThe MCP, for Claude Code