Deliver a Cross-Layer Feature with Explicit Ownership

August 8, 2026 ยท View on GitHub

Use this example when one feature spans an API, a user interface, and integration coverage. Replace the three command placeholders with existing project commands before invoking the Skill.

Goal

Deliver one end-to-end feature while preserving API compatibility and keeping backend, frontend, and verification ownership unambiguous.

Allowed scope

  • The feature's backend handler and domain logic.
  • The feature's frontend component and client integration.
  • Focused unit, integration, and end-to-end tests.
  • .raphael-loop/ checkpoint state.

Prohibited scope

  • Unrelated endpoints, screens, shared redesigns, persisted schemas, and dependency upgrades.
  • Two workers modifying the same file or owning the same deliverable.
  • Deployment, data migration, publishing, or production credentials.

Success predicates

All predicates must pass:

  1. Backend unit and contract tests pass without an incompatible API change.
  2. Frontend tests pass for loading, success, empty, and failure states.
  3. The end-to-end command proves the complete user path.
  4. An independent verifier reports no unresolved P1 or P2 correctness, security, or accessibility issue.

Verifier commands:

<backend-test-command>
<frontend-test-command>
<end-to-end-command>

Limits

  • Maximum iterations: 8
  • Maximum elapsed time: 60 minutes
  • Maximum concurrent workers: 2
  • Stop before migrations, deployment, or any external write.

Copy-ready prompt

Use $raphael-loop to deliver the requested cross-layer feature.

Build a dependency DAG with these ownership boundaries:
- Backend worker: handler, domain logic, and backend unit or contract tests.
- Frontend worker: component, client integration, and frontend states.
- Root integration: resolve the shared API contract before parallel work.
- Independent verifier: run all acceptance commands and review the resulting user path.

Allowed scope:
- Files directly required for the feature and its focused tests.

Prohibited scope:
- Incompatible public API changes, persisted schema changes, dependency upgrades, shared redesigns, deployment, and unrelated refactoring.

Success mode: all
Success predicates:
1. `<backend-test-command>` exits 0 and confirms API compatibility.
2. `<frontend-test-command>` exits 0 for loading, success, empty, and failure states.
3. `<end-to-end-command>` exits 0 for the complete user path.
4. An independent verifier finds no unresolved P1 or P2 correctness, security, or accessibility issue.

Limits:
- 8 iterations.
- 60 minutes.
- At most 2 concurrent workers with disjoint file ownership.
- No migrations, deployment, or external writes.

Persist checkpoints under `.raphael-loop/deliver-cross-layer-feature/` and stop as blocked after two iterations without measurable progress.

Expected terminal report

Require the report to identify the terminal state, task DAG and ownership, API contract evidence, all three command results, independent findings, changed files by layer, remaining blockers, and checkpoint path.