Module 3, Lesson 7: Building Out the Project in YouTrack
In this lesson, I'm taking everything we've built — the specs, the RICE prioritisation, the implementation roadmap — and using Claude Code to populate YouTrack with real, dev-ready issues. Epics, user stories, acceptance criteria, dependencies, the whole thing. By the end, we'll have a proper Agile
Module 3, Lesson 6: Set Up Claude Code + YouTrack
In this lesson, I'm picking up from the implementation roadmap we wrote in Module 3, Lesson 5 and connecting everything to our project tracking system — YouTrack — so that Claude Code can read and write issues directly. ℹ️The command used to start Claude Code with a project-specific MCP
Module 3, Lesson 5: Writing the Implementation Roadmap
In this lesson, I'm taking the Feature Priority Matrix we generated in Lesson 4 and turning it into something you can actually execute against — a phased implementation roadmap, broken down into sprints, with a risk register and release checkpoints built in. ℹ️No corrections or updates to flag
Module 3, Lesson 4: Designing RICE
In this lesson, I'm picking up right where we left off. We've got our specs in the project. Claude Code is installed. Now we need to answer the question that every product person, every founder, and honestly most engineers avoid asking until it's too
Module 3, Lesson 3: Installing Claude Code
At this point you should have your specs out and saved in your project via WebStorm. If you followed along in the previous lesson, you've got a /specs folder with feature requirements sitting in your codebase. Now we're about to add the most powerful tool in
Module 3, Lesson 2: Writing the Spec with Claude Desktop
In this lesson, we're picking up right where Lesson 1 left off. You've got WebStorm running, Claude Desktop connected via MCP, and a project folder sitting there waiting. Now we're going to use all that documentation we built in Module 2 — the research, the
Module 3, Lesson 1: Setting Up WebStorm + Claude
If you've been following along, you should have a solid stack of documentation by now — research summary, PRD, GTM, UX docs, and a user flow diagram. That's everything we built in Module 2. Now we're moving into Module 3. This is where things get
Module 2, Lesson 7: User Flow in Figma
In this lesson, we're taking everything we've generated so far — the technical doc, the UX/UI overview, the stakeholder summary, the GTM — and turning it into something visual: a user flow diagram, built directly inside Figma using Claude and MCP. ℹ️This lesson also serves as
Prompt Library
All Prompt organized
Module 2, Lesson 6: Generating the GTM Document
In the last lesson, we produced the investor summary — the document you'd hand to someone considering putting money behind your idea. Now we're doing the final piece of this documentation phase. The go-to-market document. This is your sales and marketing playbook. It's the bridge