Convert GOAL.md into a step-by-step PLAN.md with tasks and dependencies.
npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-plan
Please help me install this Agent Skill. Skill: chunk-plan Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-plan Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-plan
Converts a chunk's GOAL.md into a concrete, implementation-ready PLAN.md to guide execution.
Generate a detailed PLAN.md that translates the GOAL.md into a concrete sequence of implementation steps for the current chunk.
High-intent search queries and answers about installing and using this skill.
To generate a concrete implementation plan from a project goals document, the Skill translates your GOAL.md into a step-by-step PLAN.md. This output outlines specific tasks, execution order, and dependencies to guide the current chunk's implementation.
The best way to structure development tasks and dependencies for a new code chunk is by generating a reproducible PLAN.md. This ensures your execution steps align with repository architecture decisions and include validation checks for common edge cases.
To ensure your chunk implementation plan aligns with overall repository architecture decisions, the generated PLAN.md includes validation checks for common edge cases. This guarantees traceability and consistency with the broader project goals defined in GOAL.md.
Yes, you need a GOAL.md file before creating a step-by-step development plan. The Skill specifically parses the goals defined in GOAL.md and converts them into a concrete, implementation-ready PLAN.md to guide execution.
Planning by chunk handles edge cases and validation checks by ensuring the generated PLAN.md aligns with repository trunk decisions. This process produces a reproducible sequence of implementation steps that explicitly validates common edge cases.
A limitation of generating a PLAN.md from a high-level goals document is that the output is constrained by the scope of the current chunk. The plan focuses solely on translating GOAL.md into implementation steps without addressing cross-chunk integration.
netguy204Create a GOAL.md chunk with name, ticket, and dependencies.
ATTCKDigitalConvert plan.md and spec.md into a dependency-ordered tasks.md document.
pdovhomiljaDocument the project's technology stack, listing frameworks, databases, and third-party services.
marinkobabicRefine implementation plans by analyzing codebase gaps and correcting task dependencies.
