domains / software-engineering / autonomous-app-and-feature-build / build

build

Skill card

combined

The two skills share the name 'build' and the high-level concept of a phased pipeline, but they define fundamentally different procedures and scopes. The first skill (davepoon) is an autonomous application builder that generates, tests, and deploys a new app from a plain-English description using specific tech stacks (Next.js, FastAPI, etc.). The second skill (sickn33) is a feature development workflow for existing projects that focuses on research, planning, and tracking progress for a specific feature, explicitly referencing a detailed guide and prohibiting deployment in read-only modes. Because they address different tasks (creating a new app vs. developing a feature in an existing codebase) and have conflicting operational constraints (one deploys, the other restricts deployment), crowning one would hide a valid alternative workflow.

Repositories

Other copies

Combined skill

---
name: build
description: Unified build skill for autonomous app creation and structured feature development.
---

# Build Skill

This skill supports two distinct workflows: **Autonomous App Building** and **Feature Development**.

## 1. Autonomous App Building
Use this mode when creating a new application from a plain-English description.

**Pipeline:**
1. **Requirements**: Analyze the description.
2. **Scaffold**: Initialize the project using one of the supported stacks (Next.js + TS + Tailwind, FastAPI + Python, Express + TS, or Static HTML/CSS/JS).
3. **Implement**: Write the application code.
4. **Test**: Execute automated tests.
5. **Lint**: Ensure code quality.
6. **Security**: Run security audits.
7. **Docs**: Generate documentation.
8. **Verify**: Final validation.
9. **Deploy**: Deploy the application.

**Safety:** Enforce pre-commit validation, test coverage, and security gates.

## 2. Feature Development
Use this mode when adding a major feature to an existing project.

**Prerequisites:**
- Read the detailed guide (`references/detailed-guide.md`) before execution.
- Validate feature IDs and destination containment.

**Pipeline:**
1. **Research**: Investigate the project context.
2. **Plan**: Create a phased implementation plan.
3. **Implement**: Execute the plan.
4. **Track**: Monitor progress and phase outcomes.
5. **Verify**: Confirm phase completion.

**Constraints:**
- Do not deploy during read-only status or research phases.
- Preserve existing plans and unrelated work.
- Validate environment-specific requirements before declaring completion.

## When to Use
- **App Building**: When the user requests a new app via `/shipwright:build` or similar.
- **Feature Development**: When the user requests status, planning, or implementation of a specific feature via `/build [subcommand] [name]`.