Create implementation plans from issue titles and comments in .issues/*.toml files.
npx skills add https://github.com/glhewett/public-skills --skill issues-plan
Please help me install this Agent Skill. Skill: issues-plan Source: https://github.com/glhewett/public-skills/tree/main/issues-plan Command: npx skills add https://github.com/glhewett/public-skills --skill issues-plan
Many repository issues contain only a title and scattered comments, leaving contributors unsure how to start work or estimate complexity. This Skill automates the creation of a concise, decision-aware plan and persists it as a comment in the issue file so maintainers and contributors have immediate, reusable guidance.
Ask the agent to create a plan for issue 1 and append it as a comment to the corresponding file in the .issues directory.
High-intent search queries and answers about installing and using this skill.
This Skill automates issue planning by reading the title and comments from a TOML file in the .issues directory, generating a structured plan, appending it as a new comment, and setting the status to planned.
You can automate issue tracking by applying this Skill to your .issues/*.toml files. It processes the issue context, appends a dated comment entry from the agent, updates the status to planned, and stages the modified TOML file directly with git add for commit readiness.
The best way to generate implementation guidance is using this Skill to parse issue titles and scattered comments into a structured plan. It persists the plan directly into the issue TOML file as a comment, providing maintainers with immediate, reusable context and estimated complexity.
Yes, this issue planning workflow requires existing TOML issue files. The Skill explicitly verifies that the target issue file exists in the .issues directory before reading its contents and generating a plan, ensuring it only processes valid issue tracking data.
Yes, you can update issue status to planned and stage changes automatically. After generating the implementation plan and appending it as a comment to the TOML file, the Skill automatically sets the status to planned and stages the file using git add.
You should not use automated planning for issue tracking if your repository does not manage issues using TOML files in a .issues directory. This Skill specifically depends on reading and appending to the [[comments]] entry structure within those files to function correctly.
glhewettCreate TOML issue files with computed IDs and stage them with git.
glhewettUpdate issue status, commit changes, and create a feature branch.
glhewettAppend a chronological comment to an issue stored in .issues/*.toml.
t-miura-024Create structured GitHub Issue implementation plans from development ideas.
