simple-tasks
Install a fast local task workflow for single-project planning with `scripts/task.sh` (claim, done, status, reporting) backed by `tasks/TASKS.md` and optional `tasks/details/` notes. Use for lightweight in-progress task coordination, not full team issue tracking.
git clone --depth 1 https://github.com/robertguss/claude-code-toolkit /tmp/simple-tasks && cp -r /tmp/simple-tasks/skills/mobile-app-dev/ios-mac-app-creator/simple-tasks ~/.claude/skills/simple-tasksSKILL.md
# Simple Tasks ## Overview Paul Solt Paul@SuperEasyApps.com Version: 0.9.8 `simple-tasks` installs a lightweight local task CLI into an existing project. Design goals: - Fast local planning and execution. - Human shorthand task numbers + stable task IDs. - Single canonical backlog file: `tasks/TASKS.md`. - Optional long-form notes per task: `tasks/details/<id>.md`. ## Install ```bash skills/simple-tasks/scripts/install.sh --project-dir /path/to/project ``` Common flags: - `--project-dir PATH` required - `--mode install|upgrade` default `install` - `--dry-run` preview changes only ## Commands Installed `scripts/task.sh` supports: - `claim` - `done` - `status` - `next` - `plan` - `finished` - `upcoming` - `needs-planning` - `blocked` - `summary` - `learn` Filters: - `--today` - `--last-24h` - `--last-week` - `--last-month` - `--days` - `--mine` - `--agent` - `--limit`
Guide for creating effective skills. This skill should be used when users want
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles, business content, manifestos, or any prose requiring a clear, punchy, opinionated style.
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when users provide sample text and want to capture the voice for future use.
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.
Collaborative brainstorming partner for multi-session ideation projects. Use