skills.rest
adiytharpansa
adiytharpansaCOMMUNITY
Explore all skills by this author →
GitHub

Agentic Coding

Enforce contract-driven implementation and verification workflows for AI-assisted software development.

Updated Apr 11, 2026
Search Tags:#git#testing#code review#refactoring#software development#handoff#ai coding
One-click install
npx skills add https://github.com/adiytharpansa/Openclaw-backup --skill agentic-coding-adiytharpansa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Agentic Coding
Source: https://github.com/adiytharpansa/Openclaw-backup/tree/main/skills/agentic-coding
Command: npx skills add https://github.com/adiytharpansa/Openclaw-backup --skill agentic-coding-adiytharpansa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid unreliable AI-generated code changes by enforcing structured planning, acceptance criteria, minimal diffs, verification evidence, and reviewer-ready handoffs.

Core Features & Use Cases

  • Contract-First Implementation: Defines objectives, acceptance checks, non-goals, and constraints before code changes begin.
  • PACT Execution Workflow: Guides problem framing, acceptance design, focused change sets, and evidence-based testing for production work.
  • Use Case: Apply this Skill when fixing regressions, delivering features, handling risky refactors, or preparing code changes for review with clear validation and rollback information.

Quick Start

Ask the agentic coding skill to implement a scoped code change with an acceptance contract, verification plan, and final handoff summary.

Frequently Asked Questions about Agentic Coding

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

FAQPage Schema
How do I ensure AI-assisted code changes are reliable for production?▼

Reliable AI-assisted code changes require enforcing contract-driven implementation workflows with structured acceptance criteria, minimal change sets, evidence-based testing, and reviewer-ready handoffs before delivery.

What is the best way to prepare risky refactoring for a code review handoff?▼

Preparing a code review handoff for risky refactoring involves generating an auditable delivery checkpoint containing validation evidence, rollback information, and a focused change set based on predefined acceptance checks.

How do I implement a contract-first workflow for software development bug fixes?▼

Implementing a contract-first workflow for software development bug fixes involves defining objectives, acceptance checks, non-goals, and constraints before code changes begin, followed by evidence-based testing.

Can I use this approach to manage feature delivery with minimal diffs?▼

Yes, this approach manages feature delivery by enforcing minimal diffs through the PACT execution workflow, which guides problem framing, acceptance design, and focused change sets for production work.

Do I need acceptance criteria before starting AI coding tasks?▼

Yes, structured acceptance criteria are required before starting AI coding tasks to define objectives, non-goals, and constraints, ensuring the implementation remains scoped and verifiable.

Related Skills

Explore More Software Engineering Skills→
mortenbroesbymortenbroesby
1

spec-driven-development

Define a precise specification with objectives, constraints, and acceptance criteria before coding.

Community
Intermediate
aurora-atomsaurora-atoms

delivery-verdict-author

Assess feature delivery readiness using validation results and evidence records.

Community
Advanced
bobmatnycbobmatnyc
146

Requesting Code Review

Dispatch a code-reviewer subagent to review changes against plans and requirements.

Community
Basic
sputnikussputnikus

karpathy-guidelines

Apply behavioral guidelines for AI coding assistants to reduce common LLM mistakes.

Community
Basic