Ideate: From Daily Notes to Actionable Issues with Cursor

Developer ideation is often chaotic. Thoughts, bugs, and feature ideas strike at random times, and jotting them down in a daily scratchpad is easy. The hard part is turning that unstructured brain-dump into organized, actionable tasks. This process is manual, tedious, and ripe for automation.

This lesson demonstrates how to build a powerful, end-to-end pipeline in Cursor that bridges the gap between ideation and execution. By combining the quick-capture convenience of the Foam extension for daily notes with a custom, reusable AI rule, you can create a seamless workflow that automatically parses your thoughts, categorizes them, and generates structured issue files in your project.

You will learn to:

• Configure a Daily Scratchpad: Use Foam and a simple setting to create a dedicated, easily accessible place for your daily notes.
• Structure Your Issues: Set up a dedicated "issues" project with conventional commit-style folders (fix/, feature/, etc.) to keep tasks organized.
• Automate with a Reusable Rule: Build and refine a powerful Cursor rule that instructs an AI agent to read your daily note, extract actionable items, and create new, properly formatted issue files in the correct folders.
• Iterate for Reliability: See the importance of making rules explicit by including specific MCP tool calls to ensure the AI performs the automation reliably every time.

This workflow transforms a messy but necessary habit—jotting down daily notes—into the first, automated step of your development lifecycle, saving you time and ensuring no good idea gets lost.

Step 1: Configure Your Daily Scratchpad

By default, the Foam VS Code extension creates daily notes in your project root, which can be messy. A simple configuration in your workspace settings.json directs these notes into a dedicated folder.

// .vscode/settings.json
{
  "foam.openDailyNote.directory": "notes"
}

With this and a keyboard shortcut, you have an instant-access scratchpad to capture thoughts without cluttering your project.

Step 2: Create a Memory Project for Issues

Before automating, we need a destination. We can instruct the AI to set up a structured "memory project" to house our organized tasks.

Create a new memory project called issues in the root of my directory with a few. Folders that are named after conventional commit messages like fix and feature and chore and refactor and perf.

This creates a clear, conventional structure for our automated workflow to target.

Step 3: Extract and Organize Notes into Issues

This is the core of the automation. We prompt the agent to read the daily note, identify distinct tasks, and file them correctly in our issues project.

Please extract the content from my daily note and organize it into files inside the proper folders in my issues project. Please make sure to switch to the issues project first.

Step 4: Capture and Refine the Workflow as a Reusable Rule

To make this process repeatable, we capture it in a Cursor Rule. The initial rule might be too general, leading the AI to perform actions manually instead of using more robust, structured tools (MCPs).

We iterate and refine the rule by making it more explicit, including the exact MCP tool names for each step. This ensures the AI follows the exact, reliable procedure every time.

Refining the rule with a more specific prompt:

Please also include all the exact MCP tools that need to be used in each of the steps.

The final rule becomes a reliable, one-command solution to process your daily notes.

The Final Workflow

Once the refined rule is in place, the daily workflow is simple:

1. Jot down thoughts, bugs, and feature ideas in your daily note throughout the day.
2. At any time, start a new agent conversation.
3. Reference the rule (e.g., @create-issues-from-today).

The agent will execute the precise, multi-step process, turning your raw notes into perfectly structured and filed issues, complete with front matter and permalinks, ready for you to start working.