Structure planning conversations and save plans to docs/<context>/plans/<slug>.md.
npx skills add https://github.com/lithiumtoast/hearthportal --skill plan-lithiumtoast
Please help me install this Agent Skill. Skill: plan Source: https://github.com/lithiumtoast/hearthportal/tree/main/.claude/skills/plan Command: npx skills add https://github.com/lithiumtoast/hearthportal --skill plan-lithiumtoast
Planning conversations are often disjoint and informal, leading to scattered notes and unclear outcomes. This Skill provides a structured, repeatable method to guide conversations, generate a formal plan document at docs/<context>/plans/<slug>.md, and feed downstream skills such as /review and /build.
Tell me the task and context, and I will generate a plan saved to docs/<context>/plans/<slug>.md.
High-intent search queries and answers about installing and using this skill.
To turn planning conversations into traceable plans, you provide a task and context to generate a structured plan document automatically saved to docs/<context>/plans/<slug>.md. This ensures formal outcomes and auditability for any kind of work.
The best way to structure planning docs for downstream execution is using a standard plan template with context-aware placement. This seamlessly integrates with downstream skills like /review and /build to enact the plan effectively.
The batched-confirm workflow keeps planning docs synchronized by seeding universal and context-specific documents like glossaries and decisions. It batches these confirmations during planning to maintain consistency across saved drafts.
Yes, you can use this structured planning approach for non-code tasks like writing, presentations, and events. It is applicable to any kind of work, automatically persisting the results to the correct docs path for traceability.
Yes, this planning workflow supports amending and saving drafts. You can generate a plan, make amendments as needed, and save the draft state to the docs/<context>/plans/<slug>.md file for future reference or execution.
jmolzGenerate a Product Requirements Document from conversation content.
irahardiantoDecompose software tasks into MECE parallelizable sub-tasks with scope cards.
TheycallmehollaAudit terminology against a CONTEXT.md glossary and enforce ADR documentation.
redpanda-dataExtract writing fragments from conversations into a single markdown file.
