---
name: build
description: "Implement a feature with engine-powered context — reads only what matters"
category: workflow
tags: [implement, create, feature]
depends-on: [init]
input: "task/feature description"
output: "implemented code with minimal token usage"
token-estimate: 2000
parallel-safe: false
argument-hint: "[task description]"
user-invocable: true
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
model: claude-sonnet-4-6
context: inline
agent: general-purpose
---

# Build — Engine-Powered Implementation

Implement the requested feature. The engine provides precise context — you read only what matters.

## Precise Context (auto-generated by engine)

!`ccs context "$ARGUMENTS" 2>/dev/null || node "$HOME/.claude/skills/_ccs/engine/cli.js" context "$ARGUMENTS" 2>/dev/null`

## Steps

### 1. Use the context above
The engine already found the relevant files, symbols, and dependencies. Read ONLY the files listed in the context above. Do NOT explore or browse the codebase.

### 2. Implement
- Follow the conventions shown in the context
- Match existing code style
- Use Edit for modifications, Write for new files

### 3. Verify
- If tests exist for modified files, run them
- The index auto-updates via PostToolUse hook (no manual step needed)

## Rules
- NEVER explore beyond what the engine provided
- If the engine context is insufficient, use `ccs search "<specific term>"` or `node "$HOME/.claude/skills/_ccs/engine/cli.js" search "<specific term>"` via Bash to find more
- Read full files ONLY when you need to modify them
- After build → suggest `/ccs-test` to verify

---
*codebase-context-skill v2.0.0*