ai-coding-workflow

Executes coding tasks with repository-grounded scope, proportionate verification, and resumable progress.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sciman-top/skills-manager --skill ai-coding-workflow-sciman-top
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-coding-workflow
Source: https://github.com/sciman-top/skills-manager/tree/main/overrides/custom/ai-coding-workflow
Command: npx skills add https://github.com/sciman-top/skills-manager --skill ai-coding-workflow-sciman-top

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coding tasks often fail from unclear scope, missing verification, or lost progress across sessions. This Skill structures implementation and maintenance work around the target repository's contract so changes stay bounded, verified, and resumable. ## Core Features & Use Cases - Scoped execution: Infers the write set and minimum proof from the current diff, affected callers, and repository contract without requiring the user to supply file paths or test commands. - Proportionate verification: Matches evidence depth to risk, from focused checks for tiny changes to rollback proof for security, data, or deployment work, and distinguishes repo_verified, filesystem_projected, host_loaded, and live_accepted layers. - Resumable progress and executor selection: Recovers goal, completed work, and outstanding items on continue/resume, and selects GPT/Codex or GLM/ZCode executors by task fit rather than a fixed pipeline. - Use Case: Ask the agent to fix a bug in an API endpoint; it inspects the affected code, implements the change, runs the relevant existing tests, and reports exactly which verification layer was reached. ## Quick Start Use the ai-coding-workflow skill to implement and verify this coding task in the current repository.

Frequently Asked Questions about ai-coding-workflow

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

FAQPage Schema
How do I run a coding task with scoped verification?▼

State the authorized goal and let the skill infer the write set and minimum proof from the current diff and repository contract. It inspects, implements, and runs focused existing verification commands without requiring you to list files or tests.

How does the skill choose between GPT/Codex and GLM/ZCode?▼

It treats them as task-fit executors, not pipeline stages. GPT/Codex suits ambiguous root causes, architecture, security, or release risk; GLM/ZCode suits bounded mechanical or multi-file implementation when its host path is available.

When should I use this skill versus a code review skill?▼

Use this skill for implementation and maintenance execution where you write and verify changes. Use the dedicated review skill for review-only requests; this skill explicitly defers review-only work to it.

Does it require TDD or full test suites for every change?▼

No. Strict TDD, coverage thresholds, and full suites are not routine prerequisites. It adds tests only when they protect required behavior or an uncovered regression, and applies heavier gates when risk or repository contract demands them.

How do I resume an interrupted coding task?▼

Send a continue or resume message. The skill recovers the overall goal, completed and outstanding work, then checks current status and latest evidence before proceeding, treating new messages as steering unless they cancel the goal.

What do repo_verified and host_loaded verification levels mean?▼

They are distinct evidence layers: repo_verified means repository checks pass, filesystem_projected means files reached the target, host_loaded means the host picked them up, and live_accepted means real-world acceptance. A lower layer never proves a higher one.