skills/perform-implement-plan/SKILL.md
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.
npx skillsauth add pow-software/bytesync perform-implement-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement a previously agreed plan in ByteSync, one step at a time, while enforcing branch creation and frequent commits.
Restate the implementation plan in brief. If the plan is not present in the conversation, ask for it before starting.
Create a new branch before making any code changes. The branch name must follow ByteSync guidelines:
feature/, fix/, refactor/, docs/, or test/feature/1234-add-sync-filter)Implement the plan in small, ordered steps. After each step:
Follow the repo guidance (AGENTS.md), including:
Provide short progress updates after each step and call out any blockers or missing details before proceeding.
development
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.
development
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).
data-ai
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.
development
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.