GuideProjects & DeliveryProjects & Checklist
Projects & Delivery

Projects & Checklist

Projects group everything else together — logs, tasks, clients, and the build-step checklist purpose-built for AI-assisted coding sessions that get picked up and put down across many short sittings.

Never lose context between AI coding sessions

The checklist's core loop, session after session.

Start from a template or AI

A full step list in seconds, not an hour of planning.

Work through steps

Mark each one as you go.

Pause with a note

One required sentence: exactly where you stopped and why.

Resume instantly

Next session, read the note and continue — no re-reading the whole codebase.

Projects

The container everything else in a piece of work belongs to.

Why it exists

Logs, tasks, checklist steps, and an optional client all need somewhere to live together — a project is that home.

When to use it

Whenever you start a distinct piece of work, whether it has a client attached or not.

  1. 1

    Create a project

    Name, optional description, and a color for quick visual recognition.

  2. 2

    Link a client (optional)

    Connects it to a Client Directory entry for billing and invoicing later.

  3. 3

    Set a contract value (optional)

    Powers percentage-based milestone payments — see Clients & Invoicing.

  4. 4

    Invite collaborators

    Full team members, or scoped guests who only see this one project.

Pro Tip

Archive a project instead of deleting it once it wraps up — its history stays intact and searchable.

Build-Step Checklist

Purpose-built for AI-assisted "vibe coding" sessions.

Why it exists

A project built across many short, separate AI coding sessions loses context between them constantly. The checklist's required pause/blocked note is exactly the state an AI assistant (or you) needs to pick back up instantly.

When to use it

Any project you're building iteratively, especially alongside an AI coding assistant.

  1. 1

    Start from a template or AI-generate

    6 built-in templates (Next.js App, React Native, Node.js API, and more), or describe the project and let AI draft the steps.

  2. 2

    Organize into milestone groups

    Drag steps into renameable groups — a template applies its own groups automatically.

  3. 3

    Work through statuses

    Not Started → In Progress → Paused / Blocked (both require a short note) → Completed.

  4. 4

    Hand off or resume

    Export the whole checklist as markdown, or just reopen it next session and read the last note.

app.shipmark.io/projects/mobile-app/checklist
Milestone: Core Backend
2/5 complete
Set up Prisma schema + auth
Build project CRUD API routes
Wire checklist drag-and-drop
Client portal token auth
Waiting on design for empty state
Deploy staging environment

Pro Tip

Assign up to 10 people to a single step — each tracks their own status, and the step's overall status is computed from all of them.

Pro Tip

A required note on Paused or Blocked is the whole point: it captures exactly where you stopped, so nothing has to be reconstructed from memory.

Pro Tip

Tag steps with a project's own custom types on top of status, and link a step straight to a Scope Tracker requirement so client-approved work and checklist progress stay connected.

Milestones

Group tasks into a bigger checkpoint with its own due date.

Why it exists

Individual tasks are great for day-to-day tracking, but a milestone answers "are we on track for the bigger checkpoint" at a glance.

When to use it

Any recurring or project-wide checkpoint made up of several tasks — a sprint, a phase, a release.

  1. 1

    Create a milestone

    Name, optional description, and a due date.

  2. 2

    Attach tasks to it

    Any task can belong to a milestone.

  3. 3

    Carry over what's left

    Unfinished tasks can be moved straight to the next milestone instead of re-created by hand.

Pro Tip

Milestones and the checklist's milestone groups are separate concepts — milestones organize Tasks, groups organize checklist steps.

Best practices

  • Write the pause/blocked note as if explaining it to someone with zero context — because next session, that's effectively you.
  • Use milestone groups for anything with a natural phase structure; skip them for a short, flat list of steps.
  • Let a template do the first draft even on a project that won't match it perfectly — editing a rough list is faster than starting from nothing.

Troubleshooting

Add multiple assignees to the step (up to 10) — each tracks their own status independently, and the step's overall status is computed automatically from all of them.

Frequently asked questions

The Free plan allows up to 5 steps per project; Pro removes that limit entirely.
Yes — a direct status change is always available regardless of assignees, so there's always a manual way to correct it if the computed status is ever wrong.

Need more help?

Can't find what you're looking for here — try these.