pow-software/implementation-plan
skills/implementation-plan/SKILL.md
Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
$ install --global
skillsauthnpx skillsauth add pow-software/bytesync implementation-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 24, 2026, 8:34 PM0.4s1 file scanned
SKILL.md
- name:
- implementation-plan
- description:
- Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
Implementation Plan
Overview
Transform an existing specification into a clear, ordered implementation plan with concrete steps, affected areas, and test execution sequence. Do not write code.
Workflow
- Confirm inputs
- Ensure a specification already exists in the current context.
- If missing, ask for the spec or a link to it.
- Identify workstreams
- Break the spec into discrete steps: core logic, validation, UI, persistence, integration, tests, tooling.
- Map each step to files/areas referenced in the spec.
- Order the steps
- Prefer foundational utilities first, then integrations, then UI, then tests.
- Highlight prerequisites and dependencies between steps.
- Define test strategy
- List the test layers to update (unit/integration/e2e).
- Specify the target projects and key scenarios.
- Include build/test command order when relevant.
- Call out risks and checkpoints
- Note migration or compatibility concerns.
- Identify risky changes that warrant extra verification.
Output Format
- Title
- Assumptions
- Step-by-step plan (numbered)
- Files/Areas to touch (bulleted)
- Test plan (bulleted)
- Risks/Checkpoints
Constraints
- Do not generate code.
- Ask questions only if the specification is missing or ambiguous.
- Keep plan concise but actionable.
Related Skills
pow-software/perform-implement-plan
development
VerifiedTrustedCommunity
Execute an implementation plan end-to-end in the ByteSync repo. Use when the user asks to implement a previously established plan step by step, requires creating a branch before coding, expects regular commits during progress, and wants build/test validation.
153SKILL.mdUpdated Apr 24, 2026
pow-software/gh-issue-specifier
development
VerifiedTrustedCommunity
Analyze a GitHub issue in depth and produce a detailed specification based on codebase analysis. Use when given a GitHub issue URL or number and asked to deeply analyze requirements, scan the repository, and write a structured spec (no code changes).
153SKILL.mdUpdated Apr 24, 2026
pow-software/create-pr
data-ai
VerifiedTrustedCommunity
Push the current branch and create a Pull Request for ByteSync. Use when the user wants the agent to push a branch and open a PR, and requires the PR title and description in English.
153SKILL.mdUpdated Apr 24, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026