<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Planning on Vibe Coding</title><link>https://vibecoding.rest/tags/planning/</link><description>Recent content in Planning on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/planning/index.xml" rel="self" type="application/rss+xml"/><item><title>Sequential Thinking</title><link>https://vibecoding.rest/mcp-servers/sequential-thinking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/sequential-thinking/</guid><description>&lt;p&gt;The Sequential Thinking server provides a single tool that lets an agent externalize a chain of reasoning as discrete, revisable steps rather than reasoning silently in one pass. The host model decides when to call it, and can branch, revise, or extend earlier steps as its understanding develops.&lt;/p&gt;</description></item><item><title>Notion Spec-to-Implementation Skill</title><link>https://vibecoding.rest/skills/notion-spec-to-implementation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/notion-spec-to-implementation/</guid><description>&lt;p&gt;This curated Codex skill turns a Notion spec document directly into an implementation plan and pull request.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Specs often live in Notion, separate from the codebase, which means implementation work starts with manually re-reading and re-typing the spec. A skill that reads Notion directly removes that translation step.&lt;/p&gt;</description></item></channel></rss>