KS
Killer-Skills

plan-update — Categories.community

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing automated planning note updates and Git version control integration. SDL3 play project (vibe coding)

tony tony
[0]
[0]
Updated: 3/5/2026

Quality Score

Top 5%
31
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add tony/sdl3-playproject

Agent Capability Analysis

The plan-update MCP Server by tony is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion.

Ideal Agent Persona

Perfect for Development Agents needing automated planning note updates and Git version control integration.

Core Value

Empowers agents to update planning notes and commit documentation changes using Git commands, such as git branch, git status, and git log, while also interacting with Markdown files like UNREAL_CONVERSION_PLAN.md.

Capabilities Granted for plan-update MCP Server

Updating planning notes with current Git branch information
Committing changes to UNREAL_CONVERSION_PLAN.md
Automating documentation updates with git log output

! Prerequisites & Limits

  • Requires Git installation and configuration
  • Needs access to filesystem for notes and documentation files
  • Limited to Markdown file format for planning notes
Project
SKILL.md
960 B
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Plan Update

Update planning notes and commit documentation changes.

Context to gather

Run these commands and include the output:

  • git branch --show-current
  • git status --short
  • git log -n 10 --oneline
  • ls -la notes 2>/dev/null || echo "No notes directory"
  • ls -la UNREAL_CONVERSION_PLAN.md 2>/dev/null || echo "No UNREAL_CONVERSION_PLAN.md"

Your task

  1. If notes/plan.md exists, read it fully and update status markers
  2. If there is no notes plan, update UNREAL_CONVERSION_PLAN.md with current progress
  3. Cross-reference with recent commits to mark completed items
  4. Add new items discovered during recent work
  5. Commit independently:
docs(notes) update plan status for <topic>

why: Keep plan in sync with actual progress
what:
- Mark <items> as completed
- Add <new items> discovered

Important:

  • Do NOT start implementation
  • Only update notes/plan docs
  • Keep the commit focused on documentation changes only

Related Skills

Looking for an alternative to plan-update or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
Design

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication