Builder Skill

Translates task specifications into implementation guidance for apps/.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/larus-peritus/pel_web --skill builder-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Builder Skill
Source: https://github.com/larus-peritus/pel_web/tree/main/.claude/skills/builder-skill
Command: npx skills add https://github.com/larus-peritus/pel_web --skill builder-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams convert task specifications into concrete implementation steps, ensuring code aligns with specs, context, and app structure.

Core Features & Use Cases

  • Context-driven guidance: Leverages context/architecture.md and context/IMPLEMENTATION_STATUS.md to prevent duplication and misalignment.
  • Spec-driven execution: Reads specs/[feature]-requirements.md, specs/[feature]-design.md, and specs/[feature]-tasks.md to drive implementation within apps/.
  • Documentation and progress tracking: Updates context after tasks are completed and marks progress for traceability.

Quick Start

Review the task in specs/[feature]-tasks.md, read the relevant context files, and follow the step-by-step guidance to implement the feature under apps/[app-name]/ with tests and updated documentation.

Frequently Asked Questions about Builder Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement app features from task specs?

To implement app features from task specs, you follow a spec-driven workflow that reads context files, analyzes specs, writes code and tests in the apps/ directory, and updates documentation to ensure code aligns with specs and app structure.

What is spec-driven implementation for app development?

Spec-driven implementation is a development workflow that reads requirements, design, and task markdown files to drive systematic feature development within apps/, ensuring code aligns with project context and specifications.

How do I prevent code duplication when building new app features?

To prevent code duplication when building app features, you leverage context/architecture.md and context/IMPLEMENTATION_STATUS.md files to provide context-driven guidance that ensures new implementations align with existing architecture and prevents misalignment.

What is the best way to track implementation progress for feature tasks?

To track implementation progress for feature tasks, you update context files and mark tasks as complete after writing code and tests, providing documentation and progress tracking that ensures traceability for completed feature development steps.

Do I need specific context files to start systematic feature development?

Yes, you need specific context files to start systematic feature development. You must review tasks in specs/[feature]-tasks.md and read relevant context files like architecture.md and IMPLEMENTATION_STATUS.md before guiding implementation under apps/[app-name]/.