scoped-coder

Implements one approved Work Block write-set with scoped edits and checks.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill scoped-coder-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scoped-coder
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/.opencode/skills/scoped-coder
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill scoped-coder-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents uncontrolled code changes by confining an AI coding agent to a single approved write-set, enforcing governance gates before any file is modified. ## Core Features & Use Cases - Scoped Editing: Reads all source and docs but writes only within the approved Work Block paths, refusing commits, pushes, and secret access. - Gate Verification: Confirms the write gate is READY and the target path is inside the approved write-set before editing, and preserves unrelated work via git status inspection. - Structured Return Status: Reports DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED with changed paths, checks run, and residual risks. - Use Case: An orchestrator assigns a Work Block to add an API route; the coder implements only the approved files, runs lint and typecheck, and hands the exact diff to assurance. ## Quick Start Ask the agent to implement the approved Work Block write-set for your feature and report the changed paths and checks run.

Frequently Asked Questions about scoped-coder

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

FAQPage Schema
How do I implement an approved Work Block write-set with an AI agent?▼

Assign one Coder per write-set: it reads the Work Block, specification, plan, and acceptance criteria, confirms the write gate is READY, then edits only the approved paths. It returns DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED with changed paths and checks run.

What is a scoped coder agent in a governed SDLC workflow?▼

A scoped coder is a Coder-role agent restricted to a single approved write-set. It can read all source and run scoped checks like lint, typecheck, and tests, but cannot commit, push, deploy, or write outside approved paths.

Can the scoped coder commit or push changes to git?▼

No. The scoped coder may run read-only git commands like status, diff, and log, but git commit, git push, and destructive Git operations are forbidden. The exact revision or diff is handed to assurance instead.

Does an OpenCode edit permission prompt count as Work Block approval?▼

No. OpenCode permission prompts such as 'edit: ask' are guardrails, not Work Block approval. The agent must not use an approval prompt to expand scope beyond the approved write-set.

What are the limitations of the scoped coder approach?▼

It cannot access .env files, secrets, or credentials, install unapproved dependencies, or modify evidence to hide failed checks. Work outside the approved write-set must be escalated to the Orchestrator as a blocker.