jim60105/implement-local-plan
skills/implement-local-plan/SKILL.md
Implement a development plan from local plan files with work report tracking. Use when the user wants to execute a local development plan from `.github/plans/` or `.github/reports/`, implement backlog items step by step, or create work reports for completed tasks.
$ install --global
skillsauthnpx skillsauth add jim60105/copilot-prompt implement-local-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 9:49 AM9.1s1 file scanned
SKILL.md
- name:
- implement-local-plan
- description:
- Implement a development plan from local plan files with work report tracking. Use when the user wants to execute a local development plan from `.github/plans/` or `.github/reports/`, implement backlog items step by step, or create work reports for completed tasks.
Implement Local Plan
Implement a development plan from local plan files with systematic work report tracking.
Key Directives
- Git commit after completing work, using conventional commit format for the title and a brief description in the body. Always commit with
--signoff. Write the commit in English. - Commit the report file together with the code changes, using the templates provided in
.github/reports/.
Work Report Protocol
Development progress is tracked within the .github/reports directory. Before starting any new work, review prior reports to stay aligned with ongoing development. Treat all past reports as immutable references — do not edit or revise them. Upon task completion, generate a new comprehensive work report. Refer to naming conventions of existing files to determine an appropriate filename.
Reports must include a detailed account of the work performed, encompassing all relevant code modifications and corresponding test outcomes.
Implementation
Implement the plan step by step, following the instructions provided in the plans/ directory. Each step should be executed in sequence, ensuring that all requirements are met and documented appropriately.
Related Skills
jim60105/documentation-writer
development
VerifiedTrustedCommunity
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
19SKILL.mdUpdated May 29, 2026
jim60105/doc-coauthoring
testing
VerifiedTrustedCommunity
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
19SKILL.mdUpdated May 29, 2026
jim60105/docsify
tools
VerifiedTrustedCommunity
Comprehensive guide for building, configuring, customizing, and deploying Docsify documentation sites. Use when the user wants to (1) initialize a new Docsify site, (2) add or organize Markdown pages, sidebars, navbars, or cover pages, (3) configure `window.$docsify` options, (4) customize themes / CSS variables / fonts, (5) install built-in or third-party Docsify plugins (search, GA, emoji, zoom, copy-code, comments, pagination, tabs, etc.), (6) write a custom Docsify plugin using lifecycle hooks, (7) use Docsify Markdown helpers (callouts, link attributes, image attributes, heading IDs, task lists, embed files with `:include`), (8) deploy to GitHub Pages, GitLab Pages, Netlify, Vercel, Firebase, Docker, Nginx, etc., (9) enable PWA / offline mode, virtual routes, or Vue compatibility, or (10) upgrade a Docsify site from v4 to v5. Triggers on mentions of "docsify", "_sidebar.md", "_navbar.md", "_coverpage.md", "$docsify", or `docsify-cli`.
19SKILL.mdUpdated May 28, 2026
jim60105/chinese-content-writing-guideline
testing
VerifiedTrustedCommunity
Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content. Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for tone, style, and terminology compliance.
19SKILL.mdUpdated Apr 6, 2026