LandonSchropp/skills/planning
skills/planning/SKILL.md
Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.
$ install --global
skillsauthnpx skillsauth add LandonSchropp/agent-toolkit skills/planningInstall 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 23, 2026, 11:51 PM140.7s3 files scanned
SKILL.md
- description:
- Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.
- allowed-tools:
- Read, Write, Edit, Glob, Grep, EnterPlanMode, Skill
- agent:
- Plan
Planning
Workflow
-
If the scope of the plan is not clear from the arguments or previous context, ask the user: "Please describe the plan or provide a Linear issue ID, Linear issue URL, Linear branch name, or Sentry issue URL (for bug-fix)." If the user responds with a Linear issue or branch name, fetch the issue details using the Linear MCP server. Linear branch names follow the pattern
[team-prefix]/[ISSUE-ID]-descriptionor[ISSUE-ID]-description(e.g.,landon/eng-123-fix-loginoreng-123-fix-login) — extract the issue ID with the regex[A-Za-z]+-\d+and uppercase it. If the user provides a Sentry issue URL (bug-fix only), store it for use in the plan template. -
Determine the feature branch. If the user provided a Linear branch name, use it as the feature branch. If the user provided a Linear issue (without a branch), use the branch specified in the issue. If the current branch is the default branch (main/master), ask the user: "What feature branch would you like to use?" Otherwise, ask the user: "Would you like to use
{current_branch}as the feature branch?" -
If the current branch is the feature branch, move on to step 4. Otherwise, ask the user: "Would you like to use
{current_branch}as the base branch?". Then callscripts/create-feature-branch.shwith the feature branch and the base branch. -
Create a plan file using
scripts/generate-plan-template.ts. This will generate a pre-populated plan for you to fill out. Read the resulting file. -
Identify relevant skills for executing the plan. Review the available skills and determine which apply to the work (e.g.,
git-commit,git-pull-request,testing-typescript). Replaceexamplein the Skills section with each applicable skill on its own list item. -
Fill out each section of the plan one at a time. Follow the instructions in the template for each section.
- CRITICAL: DO NOT edit a Claude plan file in
.claude/plans. Only edit the plan template file that was generated. - If this is a new branch with no existing work, remove the Context section entirely. If resuming work on an existing branch, summarize what has already been done by running
git logandgit diffto see commits and changes. - For the Scope and Plan sections, research the plan and its implementation. Ask the user clarifying questions if needed to understand the task and what's required to implement it.
- Do not modify sections that contain the comment "Copy this section exactly as written, without modification", but do delete the comment.
- CRITICAL: DO NOT edit a Claude plan file in
-
After the plan is complete, invoke the
neovimskill and open the plan file in Neovim so the user can review it.
ultrathink
Related Skills
LandonSchropp/stacked-pull-requests
tools
VerifiedTrustedCommunity
Use when working with a stack of GitHub pull requests — creating branches, keeping the stack in sync, or merging in order. Covers Git Town setup, PR targeting, rebasing, and landing the stack.
1SKILL.mdUpdated Jun 4, 2026
LandonSchropp/plugins/ls-typescript/skills/testing-bun
tools
VerifiedTrustedCommunity
Use when writing or modifying tests in a Bun project
1SKILL.mdUpdated Jun 1, 2026
LandonSchropp/npm-publish
tools
VerifiedTrustedCommunity
Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).
1SKILL.mdUpdated Jun 1, 2026
LandonSchropp/plugins/ls-git/skills/merge-worktree
tools
VerifiedTrustedCommunity
Use when a finished worktree's branch has been reviewed and committed and needs to land. Rebases onto the latest default branch, then either fast-forwards it into the default branch (personal direct-to-main repos) or pushes it for a pull request (shared feature-branch repos).
1SKILL.mdUpdated Jun 1, 2026