Automated summary
Executes the next highest-priority task in a project through a spec → tests → code → verification cycle, then updates the plan and project memory.
Strengths
- Enforces a clear order of work: read the PRD, pick a task, read its spec, then write tests before code
- Ends with a concrete verification gate (build, lint, tests) before marking the task done in plans/plan.md
- Records reusable learnings in memory/learnings.md for later tasks
- Deliberately scopes to a single task per invocation, keeping diffs reviewable
Limitations
- Assumes an existing, precisely named layout: specs/prd.md, plans/plan.md, specs/, memory/learnings.md
- Output quality depends entirely on how precise the supplied specifications are
- Covers no commit, code review, or branch handling
Use it when a project already has a PRD, a plan, and written specs, and you want to advance reliably one task at a time.
Avoid it on a repo with no plan or specs, or when you need a broad exploratory change rather than a planned task.
Security analysis
SafeThe skill contains a straightforward project build workflow: reading specs and plans, writing tests and code, running tests/lint/build, and recording learnings. It does not request destructive commands, secret exfiltration, obfuscated payloads, network operations, or safety bypasses.
No concerns found
How this analysis is madeExamples
Build. Pick the next most important task from plans/plan.md, read its spec, write tests first, then implement and verify build and lint pass.Do the next task.Let's build it — complete one task from the plan, update memory/learnings.md, and stop when it's done.name: build description: Build a project by implementing the next most important task.
Build
Instructions
- Read specs/prd.md for an overview of the project.
- Read plans/plan.md, pick the next most important task and read the relevant specification from the specs directory.
- If it exists, read memory/learnings.md.
- After reading the specification create a set of tests to verify the implementation behaves correctly.
- Then create the code required to meet the specification. Verify the functionality is correct using the tests.
- Before marking the task as done in plans/plan.md ensure the code builds and lints without issue. All tests must pass.
- If you learn anything that will be needed for future tasks, record it in memory/learnings.md.
- Stop after completing one task.
Examples
Build. Do the next task. Let's build it. Go build.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/build-implement-next-task-mse7inu7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/build-implement-next-task-mse7inu7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/build-implement-next-task-mse7inu7/download' --output '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md.part' && mv '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md.part' '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md' && test -s '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/build' && cp -R '.skill-downloads/build-implement-next-task-mse7inu7' '.claude/skills/build'Cursor
test -f '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md' && test -s '.skill-downloads/build-implement-next-task-mse7inu7/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/build' && cp -R '.skill-downloads/build-implement-next-task-mse7inu7' '.cursor/skills/build'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/build-implement-next-task-mse7inu7'openskills read 'build-implement-next-task-mse7inu7'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/build-implement-next-task-mse7inu7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.