Transform vague requirements into structured implementation plans with units, files, tests, and risks.
npx skills add https://github.com/JesusFilm/core --skill ce-plan-beta
Please help me install this Agent Skill. Skill: ce:plan-beta Source: https://github.com/JesusFilm/core/tree/main/.claude/skills/ce-plan-beta Command: npx skills add https://github.com/JesusFilm/core --skill ce-plan-beta
Translate vague feature descriptions and requirements into a structured, implementation-ready plan that aligns with repository patterns and organizational standards.
Provide a clear planning input (feature description or requirements doc path) and request ce:plan-beta to generate a durable implementation plan.
High-intent search queries and answers about installing and using this skill.
To create an implementation plan from vague requirements, provide a feature description or user story to generate a structured document defining implementation units, file paths, dependencies, and acceptance criteria.
Standardizing software engineering planning docs is achieved by applying a standardized plan template that enforces explicit units, tests, risks, and decisions, ensuring consistent cross-team communication and handoffs.
Generating test scenarios and acceptance criteria from a feature brief involves transforming the brief into an implementation-ready plan that explicitly outlines required test scenarios and verification criteria.
Yes, you can use a standardized template for planning software implementation units, which outputs a durable plan document in docs/plans containing defined units, dependencies, and risk notes.
An implementation-ready plan for a new feature should include explicit implementation units, file paths, dependencies, test scenarios, acceptance criteria, risk notes, and recorded decisions.
Yes, this planning approach works for brainstorming outputs and improvement ideas by transforming them into a structured, implementation-ready plan with defined units, tests, and justification.
nixlimGenerates structured feature specifications and implementation plans from briefs with traceability matrices.
darrencrotonImplement code features strictly within an implementation-plan document's boundaries.
benjaminshoemakerScan codebases for dependency vulnerabilities, risky patterns, and secrets.
BradliebsTransform feature descriptions into structured implementation plans with repo-relative file paths.
