Generate implementation plans with tasks, tests, and acceptance criteria.
npx skills add https://github.com/usetheodev/theo-ui --skill to-plan
Please help me install this Agent Skill. Skill: to-plan Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/to-plan Command: npx skills add https://github.com/usetheodev/theo-ui --skill to-plan
The To-Plan skill translates a chat context and governance rules into an actionable plan that guides implementation, reducing guesswork during project execution.
Use a topic slug to generate a complete plan skeleton you can review and merge.
High-intent search queries and answers about installing and using this skill.
To generate an implementation plan from conversation context, use a topic slug to transform the current chat into a structured plan saved under knowledge-base/plans/. The plan includes goals, ADRs, tasks, tests, and acceptance criteria ready for review and execution.
You can create ADRs and quality-gates by letting the planner auto-consider matching patterns skills and project rules stored in rules/. It evaluates these inputs to inform architectural decisions and documentation within the generated plan.
A Baseline Context with file touchpoints anchors proposed changes in your repository by identifying current callers and affected files. It is produced automatically during plan generation to ground the implementation tasks in the actual codebase.
Yes, you can automate workflow planning without manual documentation by using a topic slug to generate a complete plan skeleton. The system automatically translates the chat context and governance rules into a structured plan with tasks, tests, and DoD.
The best way to turn a chat conversation into a project plan is to use a planning skill that parses the current conversation context, cross-references existing project rules, and outputs a structured implementation plan with defined acceptance criteria and tests.
Yes, a knowledge base directory is needed because the generated implementation plans are saved under knowledge-base/plans/. This directory structure ensures plans are stored alongside other project references for easy review and execution.
korchasaExplain Cursor Desktop architecture and configure AGENTS.md, rules, skills, commands, subagents, MCP, and hooks.
photonics-dhlConvert project requirements into a task-level implementation plan with file paths, code skeletons, and tests.
ngocsangyemValidate approved plans against eight quality dimensions and output pass/fail reports.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
