Run any Skill in Manus with one click

Get Started

orca-build

Stars4

Forks0

UpdatedJune 25, 2026 at 15:29

Implement planned changes with scoped edits, verification, and respect for existing project patterns.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

henryvn27

henryvn27/orca-framework

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	orca-build
description	Implement planned changes with scoped edits, verification, and respect for existing project patterns.

ORCA Framework Build

What This Skill Is

The implementation workflow for ORCA Framework.

Trigger

Use when the user has asked for code, docs, scripts, or repository changes.

Do Not Trigger

Do not use when the user only wants brainstorming, review, or research.

Required Inputs

Task or spec

Optional Inputs

Plan
Test commands
Existing artifacts

Exact Workflow

Confirm the approved scope from Linear or the opt-out record.
Before non-trivial repo edits, follow docs/version-control.md: inspect repo root/status/current/default branch, preserve unrelated dirty work, and move implementation to a scoped non-protected branch.
Read relevant files before editing.
Preserve user changes and existing patterns.
Make the smallest coherent change that satisfies the phase.
For user-facing async data, include loading, empty, and error states; prefer skeleton frames when the eventual layout is known and the surface would otherwise look blank.
If the user wants the official wrapped execution pack and Superpowers is the stronger fit, route that segment there instead of reproducing the upstream workflow locally.
Run appropriate verification.
Record what changed and what could not be verified in the durable record, including branch or PR links when repo work changed files.

Expected Outputs

Completed file changes
Verification notes
Updated artifacts or Linear comments when applicable

Quality Bar

The work should be maintainable by the repo's existing standards and should not leave hidden scaffolding. User-facing async work should not feel visually broken while data is in flight.

Common Failure Modes

Rewriting unrelated systems.
Implementing directly on a protected branch.
Skipping verification.
Leaving generated claims unsupported.

Relationship To Other ORCA Framework Skills And Commands

Used by orca-build; may pair with orca-superpowers; followed by review and QA skills.

More from this repository

same repository

orca-goal-prompt

henryvn27/orca-framework

Create a host-native `/goal` prompt for bounded ORCA plan work, especially when the user wants an agent to keep working through ready ORCA plans, delegate blocker fixes to subagents, record true blockers, and move on without stalling.

2026-06-304

orca-delegation

henryvn27/orca-framework

Create bounded delegation briefs and structured executor returns for ORCA Framework workflows.

2026-06-254

orca-ship

henryvn27/orca-framework

Prepare release readiness checks, release notes, rollback guidance, and handoff.

2026-06-254

orca-accounting

henryvn27/orca-framework

Record time, retries, and optional token, cache, and cost metrics for ORCA Framework workflows without fabricating precision.

2026-06-034

orca-adaptive-guidance

henryvn27/orca-framework

Provide lightweight, skill-sensitive coaching without slowing down normal ORCA Framework execution.

2026-06-034

orca-approval-gate

henryvn27/orca-framework

Decide when risky work must pause for approval and record the approval request clearly.

2026-06-034

name	orca-build
description	Implement planned changes with scoped edits, verification, and respect for existing project patterns.

ORCA Framework Build

What This Skill Is

The implementation workflow for ORCA Framework.

Trigger

Use when the user has asked for code, docs, scripts, or repository changes.

Do Not Trigger

Do not use when the user only wants brainstorming, review, or research.

Required Inputs

Task or spec

Optional Inputs

Plan
Test commands
Existing artifacts

Exact Workflow

Confirm the approved scope from Linear or the opt-out record.
Before non-trivial repo edits, follow docs/version-control.md: inspect repo root/status/current/default branch, preserve unrelated dirty work, and move implementation to a scoped non-protected branch.
Read relevant files before editing.
Preserve user changes and existing patterns.
Make the smallest coherent change that satisfies the phase.
For user-facing async data, include loading, empty, and error states; prefer skeleton frames when the eventual layout is known and the surface would otherwise look blank.
If the user wants the official wrapped execution pack and Superpowers is the stronger fit, route that segment there instead of reproducing the upstream workflow locally.
Run appropriate verification.
Record what changed and what could not be verified in the durable record, including branch or PR links when repo work changed files.

Expected Outputs

Completed file changes
Verification notes
Updated artifacts or Linear comments when applicable

Quality Bar

The work should be maintainable by the repo's existing standards and should not leave hidden scaffolding. User-facing async work should not feel visually broken while data is in flight.

Common Failure Modes

Rewriting unrelated systems.
Implementing directly on a protected branch.
Skipping verification.
Leaving generated claims unsupported.

Relationship To Other ORCA Framework Skills And Commands

Used by orca-build; may pair with orca-superpowers; followed by review and QA skills.