From Idea to Backlog with AI

AI Integrations

Most project management guides assume you already have stories. This one starts earlier — before the first story exists, before the sprint is created. All you have is an idea.

This guide follows two characters: Deploy Dino, a CTO launching a brand-new product, and Story Sprout, a PM who needs to turn a feature request into a sprint-ready story before tomorrow's planning session. Both start with nothing but words.

Before you start: create your Silverile project in the web UI first, then come back here. Once the project exists, your AI connects to it in seconds.

Path A — Full product brief to backlog

DD
Deploy Dino
CTO & Co-founder, Zephyr
Sunday evening — Silverile project just created

Deploy Dino is building Zephyr — a real-time collaborative whiteboard for distributed engineering teams. Think Miro, but purpose-built for async standups and technical diagramming. The Silverile project exists but it's empty. No stories, no sprint, no team. Deploy Dino opens Claude with a product brief and starts talking.

Deploy Dino says
"Show me my available Silverile projects"
Monty

I found 2 projects in your account:

  • Zephyr — Project ID: 18
  • Personal sandbox — Project ID: 3

Which would you like to set as your default?

Deploy Dino says
"Set Zephyr as my default"
Monty
Done. All requests will now use the Zephyr project.

Connected. Now Deploy Dino pastes the full product brief — description, core features, and tech stack — and asks Monty to break it down.

Deploy Dino says
"Here's the Zephyr brief. Break this into sprint-ready stories for v1. Product: Zephyr — real-time collaborative whiteboard for distributed engineering teams. Stack: React + TypeScript (Vite), Node.js WebSocket server, PostgreSQL + Redis, Docker, AWS ECS, Auth0. Core features: — Infinite canvas: shapes, sticky notes, freehand drawing, text blocks — Real-time multi-user sync with live cursors and presence list — Rooms and boards: create, name, share via link — Export board to PNG — Version history: snapshot on save, restore previous version — Auth0 login (Google + GitHub OAuth)"
Monty

Here's a proposed v1 breakdown for Zephyr. Review before I create anything:

#StoryPts
1Auth0 authentication — Google + GitHub OAuth, session management, logout5
2Infinite canvas engine — shapes, sticky notes, freehand drawing, text blocks8
3Real-time sync — WebSocket server, Redis pub/sub, conflict resolution8
4User presence — live cursors, user list overlay, join/leave events5
5Room and board management — create, rename, share link, delete3
6Export board to PNG — full canvas capture, download trigger3
7Version history — snapshot on save, list versions, restore previous5

Total: 37 points. Create all 7? (yes / edit / skip one)

Deploy Dino says
"Yes, create all of them"
Monty

Creating stories one at a time — previewing each before saving.

[Monty previews each story; Deploy Dino confirms. After all 7 are confirmed:]

  • #2180 — Auth0 authentication
  • #2181 — Infinite canvas engine
  • #2182 — Real-time sync
  • #2183 — User presence
  • #2184 — Room and board management
  • #2185 — Export board to PNG
  • #2186 — Version history

All 7 stories created and linked to the Zephyr project.

Deploy Dino says
"Add all of them to Sprint 1"
Monty

Added all 7 stories to Sprint 1 (Zephyr · Sprint 1).

#2180 · #2181 · #2182 · #2183 · #2184 · #2185 · #2186 — all In Backlog, ready to assign.

Deploy Dino says
"Generate test cases for story 2180 and 2181"
Monty

Test cases for #2180 — Auth0 authentication:

  • TC-01 · Google OAuth login — success path redirects to canvas
  • TC-02 · GitHub OAuth login — success path redirects to canvas
  • TC-03 · OAuth failure shows user-friendly error, not raw response
  • TC-04 · Session persists on page refresh
  • TC-05 · Logout clears session and redirects to login

Test cases for #2181 — Infinite canvas engine:

  • TC-01 · Rectangle, circle, and sticky note render at correct position
  • TC-02 · Freehand stroke appears in real time as mouse moves
  • TC-03 · Text block accepts input and saves on blur
  • TC-04 · Canvas pans smoothly with click-drag on empty space
  • TC-05 · Zoom in/out with scroll wheel keeps shapes in relative position

In one conversation: project connected, 7 stories created, sprint populated, 10 test cases generated. Deploy Dino didn't open a ticket template or copy-paste a single line.

The brief you give Monty becomes the source of truth — story titles, acceptance criteria, and test cases all trace back to it. Include tech stack details and Monty will reference them in the acceptance criteria.

Path B — Single feature brief to story

SS
Story Sprout
Product Manager, Code Koalas
Tuesday afternoon — feature request just confirmed

Story Sprout has a feature request that came out of a user interview: notification preferences. Users want to control which Silverile events trigger email notifications. Story Sprout has bullet points in a Notion doc and needs a story before tomorrow's planning session.

Story Sprout says
"Turn this into a story: Notification preferences — users can choose which events trigger email notifications. Events: story assigned to me, story status changed, defect created on my story, sprint started. Each toggle is on/off. Settings saved per user, per project."
Monty

Story preview:

  • Title: Notification preferences — per-user email controls
  • Points: 5
  • Description: Users can enable or disable email notifications for individual event types. Settings are saved per user per project and take effect immediately.
  • Acceptance criteria:
    • Preferences page shows four toggles: story assigned, status changed, defect created, sprint started
    • Toggling off an event stops that email immediately
    • Settings are per-project — different projects can have different preferences
    • Default state: all notifications on for new users
    • Preference changes are saved without a page reload

Create this story? (yes / no)

Story Sprout says
"Yes — and add it to the current sprint and generate test cases"
Monty

Story #2187 created. Added to Sprint 25. Generating test cases:

  • TC-01 · All four toggles render on the preferences page
  • TC-02 · Disabling "story assigned" stops that email within one event cycle
  • TC-03 · Settings persist after page refresh
  • TC-04 · Project A preferences do not affect Project B preferences
  • TC-05 · New user sees all toggles on by default

One prompt. One story, fully specified, in the sprint, with five test cases. Story Sprout pastes the Silverile story link into the Notion doc and closes the tab.

Quick reference

PromptWhat it does
"Show me my available Silverile projects"Lists all projects you have access to — pick one to set as default
"Set Zephyr as my default"Connects AI to that project for all subsequent requests
"Here's my product brief: [description + tech stack]. Break this into sprint-ready stories."AI proposes a full story breakdown as a table — review before anything is created
"Create all of them"AI creates each story one at a time with preview + confirm per story
"Add all of them to Sprint 1"Batch-adds the new stories to the sprint
"Generate test cases for story 2180 and 2181"Generates test cases for the specified stories
"Turn this into a story: [feature description]"Creates one story from a plain-English brief with full AC
"Yes — and add it to the current sprint and generate test cases"Confirms story creation, adds to sprint, and generates test cases in one reply

For day-to-day sprint work — developing stories, running tests, filing defects, and managing sprints — see the Build & Track with Silverile and AI guide.