Breaks down a plan or technical spec into dependency-ordered implementation issues — as local markdown files under docs/issues/, or as GitHub sub-issues of the parent spec issue with native blocking.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "plan-or-spec-to-issues" with this command: npx skills add jason-ezenwa/skillsmp-jason-ezenwa-jason-ezenwa-plan-or-spec-to-issues
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Implements a feature based on a provided technical specification, ensuring build stability and strict adherence to the spec through a sub-agent code review. Creates a feature branch, commits changes, and raises a PR on completion.
Autonomously plans, specs, implements, and raises a PR for a task — without requiring the human to be present for the planning phase. Use this skill when the user hands off a task and asks you to handle it end-to-end, or when phrases like "auto-implement", "handle this autonomously", "fire and forget", or "work on this without me" appear. Also use when the user provides a task description and signals they want to review the output rather than participate in the planning.
Interview the user relentlessly about a feature or idea until reaching shared understanding, then produce a plan or spec. Use before generating a plan or speccing out a feature when requirements are unclear or not yet defined, or when "grill me" is mentioned.
Add new functionality to untested legacy code using Sprout Method, Sprout Class, Wrap Method, or Wrap Class — whichever best fits the dependency profile. Use...