Create testable work plans with acceptance criteria and execution handoffs.
npx skills add https://github.com/lpjhelder/kronon-forge --skill plan-lpjhelder
Please help me install this Agent Skill. Skill: plan Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/plan Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill plan-lpjhelder
Planning prevents wasted effort, scope creep, and missed edge cases by turning vague or broad requests into concrete, testable work plans and clear handoffs for execution. The plan skill structures discovery, creates acceptance criteria, and produces implementation steps grounded in codebase evidence so execution starts from a solid foundation.
$ralph and $team without editing source code directly.Ask the plan skill to create a consensus work plan to add JWT authentication across the API, including risks, testable acceptance criteria, and an implementation roadmap.
High-intent search queries and answers about installing and using this skill.
To turn vague ideas into actionable work plans, use interactive interview mode to gather requirements one question at a time, ensuring outputs include testable acceptance criteria, file-level evidence, and explicit handoff guidance for execution agents.
A consensus review for software architecture planning runs Planner, Architect, and Critic loops to validate work. It produces formal RALPLAN-DR summaries, Architecture Decision Records, and pre-mortems for high-risk work before granting approval.
You can gather requirements for a codebase-informed roadmap using interactive interview mode, which consults lightweight codebase exploration before asking you questions, grounding the implementation steps in actual file-level evidence.
Yes, you can generate a comprehensive software project plan immediately from a detailed request using direct mode, which produces implementation steps, testable acceptance criteria, and execution handoffs without an interactive interview.
An execution handoff for implementation agents includes .forge/plans artifacts, available-agent rosters, and concrete launch hints for execution agents, ensuring the next stage starts from a solid foundation without editing source code directly.
You should use pre-mortems and quality gating during project scoping when dealing with high-risk work, enforcing sequential architect and critic checks to validate consensus reviews before approving the actionable work plan.
hotaqCreate actionable work plans with acceptance criteria and implementation steps.
tkerseyAudits codebase abstractions and proposes prioritized cuts with a migration plan.
TienchingAlias the plan workflow to run consensus planning across Planner, Architect, and Critic.
wmasfoeAutomate strategic planning with interview-driven discovery or direct plan generation.