Productivity Cycles and AI Agents
Based on CortexFutura Tools's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Create a Nano cycle super tag with fields for date, energy, Elan, and goal completion, using dropdown options for consistent logging.
Briefing
Tana’s out-of-beta release is paired with a practical system for turning focus into measurable cycles—and then feeding those records to an AI “productivity coach” that gives feedback based on what actually happened. The core idea is to structure work into repeatable time blocks (30 minutes), group three blocks into a 90-minute “brain cycle,” and log energy, motivation (“Elan”), and whether the goal was completed. That data then becomes the input for live searches and an AI agent that reviews recent cycles and suggests concrete improvements.
The build starts with a smallest unit called a “Nano cycle,” implemented as a super tag in Tana. Each Nano cycle note automatically includes fields for date, energy (configured as a dropdown using battery emojis), Elan (dropdown using fire emojis), and goal completion (checkmark vs X). To avoid re-creating the same structure every time, the fields are added to the super tag template, and default values can be set so a new cycle starts with consistent prompts.
Next comes the workflow inside each Nano cycle. A planning template prompts the user to define the goal, decide how to start, and anticipate likely distractions—plus a counter-strategy for each. After the work block, a review template asks what was accomplished, what distracted attention, and what to do better next time. Tana commands automate the mechanics: buttons appear to insert the plan and work sections, clone the review section, and auto-fill the date/time for the cycle using a relative date string (e.g., “now + 30m”). Conditions control when buttons show up—plan/start only when the date field is empty, and review only when it’s filled—so the cycle behaves like a guided checklist.
To reduce busy work during review, the system uses a live search that automatically aggregates completed tasks. When items are checked off anywhere in the plan/work sections, a “grandparents/descendants with refs” search for done items surfaces them in the accomplishments area. This means the user doesn’t have to manually copy results into the review.
The 90-minute layer (“micro cycle”) groups three Nano cycles together with short breaks. Its plan step adds an extra element: consequences of not doing the task, framed as more motivating than purely positive visualization. A live search then pulls together what was completed across the three Nano cycles, including energy/Elan changes and distraction notes.
Finally, an AI agent is wired into the workspace. A “cycle review session” tag collects micro cycles from the last day via a live search, then passes that context into a Tana agent configured with a system prompt tuned for an expert productivity coach. The agent can answer questions like what to improve, and it responds using the logged patterns—such as noticing energy and Elan dropping in a specific micro cycle and recommending more robust distraction management. The result is a feedback loop: structured logging → automated aggregation → AI coaching grounded in the user’s own recent work history.
Cornell Notes
The system builds a structured productivity loop in Tana: log work in 30-minute “Nano cycles,” group three into a 90-minute “micro cycle,” and capture energy, Elan, goal completion, distractions, and outcomes. Tana commands automate planning, starting, reviewing, and date/time filling, while live searches automatically aggregate completed tasks into the “accomplishments” section. A “cycle review session” tag collects micro cycles from the last day and feeds them to a configured AI agent acting as a productivity coach. Because the agent receives the user’s actual cycle records (not generic advice), it can give targeted feedback such as identifying when energy drops and suggesting distraction strategies. This matters because it turns focus habits into measurable data that can be iterated quickly.
How does a Nano cycle get structured so it’s fast to repeat and easy to analyze later?
What makes the Nano cycle workflow feel like a guided checklist instead of manual note-taking?
How does the system avoid manual copying of accomplishments into the review section?
What changes when moving from 30-minute Nano cycles to a 90-minute micro cycle?
How does the AI agent produce feedback that’s grounded in the user’s actual behavior?
Why are commands and live searches combined rather than relying on the AI alone?
Review Questions
- In a Nano cycle, what fields are logged, how are they configured (e.g., dropdown options), and which command fills the date/time?
- How do node filter conditions determine when plan/start vs review buttons appear during a cycle?
- What specific role do live searches play in populating the accomplishments section, and how does that affect the AI agent’s input quality?
Key Points
- 1
Create a Nano cycle super tag with fields for date, energy, Elan, and goal completion, using dropdown options for consistent logging.
- 2
Use templates plus Tana commands to automate plan insertion, start timing (relative date), and review insertion without manual restructuring.
- 3
Apply node filter conditions so plan/start buttons appear only before the date is set, and the review button appears only after the cycle is started.
- 4
Use live searches to automatically aggregate done tasks into the accomplishments section, eliminating copy/paste during review.
- 5
Group three Nano cycles into a micro cycle (about 90 minutes) and include a consequences-focused planning prompt to strengthen motivation.
- 6
Build a cycle review session that collects micro cycles from the last day via live search and passes that context into a configured AI agent for targeted coaching.
- 7
Treat the AI agent as a feedback layer on top of structured logs, so recommendations reflect energy/Elan trends and distraction patterns from real work.