Xpersona
A

Agentic Coding

CLAWHUB · Unverified

Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints. Skill: Agentic Coding Owner: ivangdavila Summary: Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints. Tags: latest:1.0.0 Version history: v1.0.0 | 2026-02-27T21:43:14.826Z | user Initial release with PACT protocol, contract templates, and handoff-first delivery workflow. Archive index: Archive v1.0.0: 8 files, 8660 bytes Files: handoff

62
Rank
84
Safety
14k
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 14.2K downloads reported by the source. Last updated 11/16/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s178jdk12x4qj3gs2se3etxf3h83h7ft:agentic-coding
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-ivangdavila-agentic-coding-c-coding-2/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

15,952 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: Agentic Coding
slug: agentic-coding
version: 1.0.0
homepage: https://clawic.com/skills/agentic-coding
description: Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints.
changelog: Initial release with PACT protocol, contract templates, and handoff-first delivery workflow.
metadata: {"clawdbot":{"emoji":"AI","requires":{"bins":["git"]},"os":["linux","darwin","win32"]}}
---

## Setup

If `~/agentic-coding/` does not exist or is empty, read `setup.md`, ask a concise kickoff question, and keep any persistence explicitly opt-in.

## Positioning

This skill is intentionally different from `agentic-engineering` and `vibe-coding`:
- `agentic-engineering` focuses on multi-agent operating patterns and team throughput.
- `vibe-coding` focuses on prompt-led exploration and fast idea shipping.
- `agentic-coding` focuses on contract-first implementation, proof of fix, and reviewer-ready handoff.

## When to Use

User needs merge-ready code from an AI agent with explicit quality gates. Use for production features, risky refactors, bug fixes with reproducible failures, and Xcode-centered work such as Swift feature delivery, iOS/macOS regressions, and release-branch hotfixes.

## Architecture

Memory lives in `~/agentic-coding/`. See `memory-template.md` for setup.

```text
~/agentic-coding/
|- memory.md       # Persistent preferences and operating mode
|- contracts.md    # Accepted task contracts and non-goals
|- evidence.md     # Test evidence and verification snapshots
`- handoffs.md     # Delivery notes and rollback hints
```

## Quick Reference

Load these files on demand to keep context focused and execution fast.

| Topic | File |
|-------|------|
| Setup process | `setup.md` |
| Memory template | `memory-template.md` |
| PACT loop | `protocol.md` |
| Contract prompts | `prompt-contracts.md` |
| Merge handoff checklist | `handoff.md` |

## Core Rules

### 1. Lock a Contract Before Writing Code
Start every task with a compact contract:
- Objective: exact outcome in one sentence
- Acceptance: checks that prove success
- Non-goals: what must stay untouched
- Constraints: stack, style, limits, deadlines

No contract, no code.

### 2. Run the PACT Loop
Use the same execution loop every time:
1. **P**roblem framing: restate objective and assumptions
2. **A**cceptance design: define checks before edits
3. **C**hange set: produce the smallest useful diff
4. **T**race and test: show evidence and residual risk

This skill is execution discipline, not brainstorming.
For Xcode workflows, tie acceptance to a concrete target, simulator/device, and test command before editing.

### 3. Keep Diffs Surgical
One user objective maps to one focused change set:
- Prefer file-local edits over broad rewrites
- Separate behavior change from style cleanup
- Avoid hidden side effects outside declared scope

If scope grows, split into a second contract.

### 4. Prove Failure Then Prove Fix
For 

_meta.json

{
  "ownerId": "kn73vp5rarc3b14rc7wjcw8f8580t5d1",
  "slug": "agentic-coding",
  "version": "1.0.0",
  "publishedAt": 1772228594826
}

handoff.md

# Merge Handoff Checklist

Use this checklist before claiming completion.

## Required Sections

1. Change Summary
- One paragraph describing the user-visible outcome

2. File Impact
- Exact file list
- Why each file changed
- Blast radius statement

3. Validation Evidence
- Commands run
- Key outputs summarized
- Before and after proof for bug fixes

4. Risk and Rollback
- Remaining risks by severity
- Rollback steps that can be executed quickly

5. Follow-ups
- Deferred cleanup or hardening tasks
- Suggested sequencing for next contracts

## Quality Bar

A handoff is complete only when a reviewer can answer:
- What was requested?
- What changed?
- Why should I trust this change?
- How do I revert safely?

memory-template.md

# Memory Template - Agentic Coding

Create `~/agentic-coding/memory.md` with this structure:

```markdown
# Agentic Coding Memory

## Status
status: ongoing
version: 1.0.0
last: YYYY-MM-DD
integration: pending

## Working Context
<!-- Active repositories and stacks -->
<!-- Typical task types and risk profile -->

## Contract Preferences
<!-- How this user defines objective, constraints, and non-goals -->
<!-- Preferred acceptance style: tests, logs, screenshots, benchmarks -->

## Validation Patterns
<!-- Commands and checks that are trusted in this workspace -->
<!-- What counts as enough evidence before handoff -->

## Repeated Traps
<!-- Recurring failure modes worth preventing early -->

## Notes
<!-- Stable operational observations only -->

---
*Updated: YYYY-MM-DD*
```

## contracts.md Template

Create `~/agentic-coding/contracts.md`:

```markdown
# Active Contracts

## YYYY-MM-DD - [Task Name]
Objective: ...
Acceptance: ...
Non-goals: ...
Constraints: ...
Status: drafted | active | verified | blocked
```

## evidence.md Template

Create `~/agentic-coding/evidence.md`:

```markdown
# Validation Evidence

## YYYY-MM-DD - [Task Name]
Before: [failing test/log/reproduction]
After: [passing test/log/reproduction]
Residual risk: [low/medium/high + why]
```

## handoffs.md Template

Create `~/agentic-coding/handoffs.md`:

```markdown
# Handoffs

## YYYY-MM-DD - [Task Name]
Changes: ...
Files touched: ...
Validation run: ...
Rollback: ...
Next action: ...
```

## Status Values

| Value | Meaning | Behavior |
|-------|---------|----------|
| `ongoing` | Default | Keep collecting patterns |
| `complete` | Context is stable | Use memory mostly for refresh |
| `paused` | User wants minimal process | Keep only essential checks |
| `never_ask` | User rejected integration prompts | Stop prompting and stay silent |

prompt-contracts.md

# Contract Prompt Templates

Use these prompts to start high quality agentic coding cycles.

## Feature Contract Prompt

```text
You are implementing one scoped feature.
Objective: [one sentence]
Acceptance checks:
1) [new behavior test]
2) [baseline must stay green]
Non-goals: [what must not change]
Constraints: [stack, style, performance, deadline]
Output:
- Plan in 3-6 bullets
- Files to modify
- Minimal diff strategy
- Validation commands
Wait for approval before coding.
```

## Bug Fix Contract Prompt

```text
You are fixing one reproducible bug.
Bug signal: [error/log/behavior]
Reproduction steps: [ordered steps]
Acceptance checks:
1) Reproduction fails before fix
2) Reproduction passes after fix
3) Related area remains stable
Non-goals: [explicit exclusions]
Output:
- Suspected root cause
- Minimal fix path
- Verification plan
Do not implement until the plan is approved.
```

## Refactor Contract Prompt

```text
You are refactoring without changing behavior.
Objective: [maintain behavior, improve structure in specific area]
Behavior lock: [tests or traces proving parity]
Constraints:
- No API signature changes
- No schema changes
- No new dependencies
Output:
- Refactor boundaries
- Risk points
- Rollback strategy
- Validation plan
Proceed only within listed boundaries.
```

## Final Handoff Prompt

```text
Prepare a reviewer handoff with:
1) What changed and why
2) Files touched
3) Validation evidence (before and after)
4) Residual risk
5) Rollback instructions
Keep it concise and auditable.
```

Sponsored

Ads related to Agentic Coding and adjacent AI workflows.