About build
build is a skill for coordinating major feature work across research, planning, implementation, and progress tracking. It organizes work into named phases and can report status and next steps.
Key features
- 01Phased feature-development workflow
- 02Research and planning support
- 03Implementation progress tracking
- 04Status and next-step reporting
Use cases
- 01Plan a major feature from research through implementation
- 02Check the status of a feature by ID
- 03Identify the next action in an ongoing feature effort
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill buildAfter installing, type/buildin Claude Code to confirm it loaded.
Bundled filesreferences/detailed-guide.md
Details
From the project READMEFeature development pipeline - research, plan, track, and implement major features.
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
- You need a structured workflow for building a major feature across research, planning, implementation, and tracking.
- The task involves moving a feature through named phases such as
research,implementation,progress, orphase. - You want one command to coordinate status, next steps, and phased delivery for a feature effort.
Example
Input: /build status export-csv for an authorized project whose implementation
plan exists but whose CSV encoding test is still failing. Output: implementation
in progress, failed encoding test and the next repair step; the presence of three
planning files does not justify claiming the feature is complete. With no slash
command support, interpret “show the status of export-csv” the same way.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Validate feature IDs and destination containment before writing. Host-specific command and question tools are optional interfaces, not prerequisites.
- Read-only status/research does not authorize deployment; existing plans and unrelated work must be preserved.