Convert SPAR outcomes into a multi-perspective PLAN.md document.
npx skills add https://github.com/tapania/5d-skills --skill 5d-plan
Please help me install this Agent Skill. Skill: 5d-plan Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-plan Command: npx skills add https://github.com/tapania/5d-skills --skill 5d-plan
This Skill converts sparring outcomes from the 5D-SDD workflow into a concrete, multi-perspective plan that guides teams before committing to technical specifications.
Create a PLAN.md document that defines the problem, proposed solution, and plan dependencies after completing the SPAR phase. Then share the PLAN.md with stakeholders for alignment.
High-intent search queries and answers about installing and using this skill.
Convert SPAR outcomes into a planning document by translating sparring results into a standalone PLAN.md that captures problem statements, proposed solutions, assumptions, and stakeholder perspectives to guide commitment before specification.
Document project assumptions and alternatives by generating a PLAN.md that records proposed solutions, thinking depth, dependencies, alternatives, quadrant coverage, and time horizons to ensure multi-perspective alignment before technical specification.
You need a multi-perspective plan when translating post-SPAR outcomes into a concrete PLAN.md, ensuring alignment across Individual Outer, Individual Inner, Collective Outer, and Collective Inner perspectives before committing to specifications.
Create a PLAN.md by defining a clear problem statement and explicit plan structure, then documenting the proposed solution, thinking depth, dependencies, alternatives, quadrant coverage, and time horizons for stakeholder review.
Yes, generating documentation requires a completed SPAR phase with a clearly defined problem statement and explicit plan structure to produce a standalone PLAN.md for stakeholder alignment and iteration.
No, this planning approach requires explicit plan structure including defined dependencies, thinking depth, assumptions, and alternatives to produce a concrete PLAN.md that effectively guides commitment before specification.
tapaniaRun structured sparring sessions to surface assumptions and counterarguments before planning.
silaslopes100Validate reverse-engineered technical specifications against source code and architectural patterns.
gharam1234Automates the TDD loop for Playwright test development.
AcidicSoilAnalyze backlog items, dependencies, and velocity to produce sprint plans and artifacts.
