Convert ambiguous software intent into validated, file-backed planning artifacts.
npx skills add https://github.com/notque/vexjoy-agent --skill planning-notque
Please help me install this Agent Skill. Skill: planning Source: https://github.com/notque/vexjoy-agent/tree/main/skills/process/planning Command: npx skills add https://github.com/notque/vexjoy-agent --skill planning-notque
This Skill prevents wasted execution by converting unclear user intent into a structured, file-backed software planning artifact with explicit scope boundaries, validation, and controlled session pause/resume.
Use planning to write a software spec and acceptance criteria from your idea by saying: Write spec for a feature that adds login with email and password, including user stories and testable acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To write a software spec from a vague idea, you convert ambiguous intent into structured artifacts containing user stories and testable acceptance criteria. This spec-first planning approach anchors downstream design and implementation by enforcing explicit scope boundaries before execution begins.
The best way to resolve project ambiguity is using an interview-style clarity pass with depth-first questioning and recommended answers. This surfaces gray areas and resolves interdependent decisions efficiently, ensuring assumptions are addressed before a file-backed plan is created.
You manage planning artifacts across sessions by using a file-backed plan workflow that creates, checks, and validates persistent files. This ensures progress survives independently of active sessions, preventing lost decisions and maintaining continuous plan lifecycle management.
Yes, you can pause mid-work and resume from handoff artifacts without losing plan state. The workflow supports stopping and restarting from persistent file-backed artifacts, ensuring all previous decisions and validation gates remain intact during session handoff.
You need plan validation gates during requirements definition when converting ambiguous intent into structured plans. These gates enforce explicit scope boundaries and validate the generated software spec, preventing wasted execution on unvalidated or incomplete user stories.
mlopscommunityConvert spoken transcripts into structured feature specifications and requirements.
epieczkoParse Markdown Epic documents and generate structured user stories as JSON.
marcuskroghGenerate structured BUG.md files with repro steps and acceptance criteria.
CinderZhangBuilds and runs Streamlit apps and React UIs for iterative visual feedback.
