project-planner
Triage ideas, problems, and feature requests into the right format: proposal doc, feature issue, or bug report. Repo-aware — discovers templates and docs structure from the current repository. Use when: (1) the user describes an idea, feature, or problem they want to track, (2) the user says "file a bug", "I have an idea", "let's plan this feature", or similar, (3) the user wants to break down a large feature into phases with GitHub issues. NOT for: actually implementing code (use coding-agent), reviewing PRs, or general questions about the codebase.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/chriscox/project-plannerWhat This Skill Does
The project-planner skill acts as your automated product manager and repository triage assistant. It bridges the gap between raw user ideas and structured technical artifacts. By intelligently analyzing your input, it determines whether a request should be drafted as a long-form design proposal, a structured feature issue, or a standardized bug report. The skill is deeply repo-aware; it inspects your local environment for configuration files like .project-planner.yml, existing GitHub issue templates, and documentation structures to ensure that every artifact it creates aligns perfectly with your team's existing conventions.
Installation
To integrate project-planner into your OpenClaw environment, ensure you have the GitHub CLI (gh) installed and authenticated. Run the following command in your terminal:
clawhub install openclaw/skills/skills/chriscox/project-planner
Once installed, the skill will automatically detect your local repository root and begin scanning for your existing documentation templates.
Use Cases
- Triage and Grooming: Quickly convert brainstorming sessions into actionable GitHub issues.
- Architectural Planning: Draft complex proposals for large feature sets that require multiple phases of implementation.
- Maintenance: Standardize bug reporting by ensuring every issue contains necessary context and follows repo-specific templates.
- Repository Hygiene: Maintain updated proposal indexes and navigation files automatically as you iterate on project ideas.
Example Prompts
- "I have an idea for a new plugin architecture that would support hot-swapping modules—can you draft a proposal for this?"
- "We keep seeing a segmentation fault when running the CI pipeline on macOS; file a bug report for this with the standard error log template."
- "Let's add a dark mode toggle to the dashboard; it's a small change, so please file a feature issue for this."
Tips & Limitations
To get the most out of project-planner, maintain a .project-planner.yml file at your repository root to explicitly map your template locations. If you aren't sure if an idea is a bug or a feature, simply ask the AI to categorize it for you. Note that this skill is strictly for project management and documentation; it will not write the actual source code or implement the logic for the features it tracks. For implementation, always switch to a dedicated coding-agent after your issues are properly filed.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-chriscox-project-planner": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, external-api