.github/skills/speckit-workflows-ultraplan-tasks/SKILL.md
Generate a deeply-reasoned, implementation-ready task breakdown for the current spec-kit feature using extended analysis.
npx skillsauth add pradeepmouli/lspeasy speckit-workflows-ultraplan-tasksInstall 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.
ultrathink
You are generating a comprehensive task breakdown for the current spec-kit feature by deeply analysing the specification and plan.
cd "$(git rev-parse --show-toplevel)" && \
source .specify/scripts/bash/common.sh && \
get_feature_paths
This provides FEATURE_DIR, FEATURE_SPEC (spec.md), IMPL_PLAN (plan.md), and TASKS (tasks.md). Load and carefully read all three files before continuing.
Conduct a thorough analysis of the specification and plan:
Overwrite $TASKS (tasks.md) with the full breakdown using this format:
# Tasks: [Feature Name]
> Generated by speckit.ultraplan — edit freely.
<!-- Clarifications (remove when resolved):
- [Any ambiguities spotted during analysis]
-->
## Implementation Tasks
- [ ] T001: [Concrete, single-concern task — one commit]
- [ ] T002: [Concrete, single-concern task — one commit]
...
Rules:
After writing tasks.md, output:
Ultraplan complete
**Feature**: [feature name]
**Tasks generated**: [N]
**Tasks file**: [absolute path to tasks.md]
### Task summary
T001 — [one-line description]
T002 — [one-line description]
...
tools
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files. Claude Code's built-in LSP tool is READ-ONLY (find references, but no rename / file-move / move-symbol). Hand-editing those refactors silently misses re-exports, aliased imports, type-only imports, and {@link} doc references. This skill drives a real language server via the `lspeasy` CLI to apply a correct WorkspaceEdit that catches every reference. Trigger when the user asks to rename a function/class/variable/type project-wide, move a file and fix its importers, or pull a symbol out into another module.
tools
Documentation site for lspeasy Use when: You are building a browser-based LSP client, a WebSocket-backed language....
tools
Documentation site for lspeasy Use when: You are implementing a custom client layer and need the same validation....
tools
Use when working with lspeasy (client, core, server). Covers: lsp, language-server-protocol, lsp-client, language-client, jsonrpc, transport, lsp-server, language-server.