Owner only dev orchestrator
Skill dzhokhov/markdown-agent-vault/skills/owner-only-dev-orchestrator
Agent-ready Markdown vault methodology with AGENTS.md, templates, skills, logs, and file-safe workflows.
npx -y skills add dzhokhov/markdown-agent-vault --skill owner-only-dev-orchestratorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
SKILL.md
2.3 KB, as published. Nobody here has run it
Owner-Only Dev Orchestrator
Appointment
Perform end-to-end contour for development tasks: contract task -> implementation -> self-test -> solution for the owner.
Related context: LLM Rules].
Mandatory sources of rules
Read before work:
- LLM Rules
- Owner-only development standard with LLM agent ]
- Protocol of creation and application of scripts ]
Workflow
- Identify the target repository/code folder.
- Check for mandatory process artifacts in the repository:
AGENT_WORKFLOW.mdTEST_PLAN.mdRELEASE_CHECKLIST.mdCHANGELOG.mdINCIDENT_RUNBOOK.md
- If there are no artifacts, create them from
meta/templates/before risky changes. - Set the task contract:
- Goal
- Scope
- Out of scope
- Risk class (
low|medium|high) - Required validations
- Follow through with small, logical steps.
- Call
$test-gatesto run quality gates. - If there is a release part, high-risk change or incident, call
$release-rollback. - Create an owner decision packet and return only the management decision.
Limitations on autonomy
- Do not perform destructive/history-rewrite actions without explicit confirmation.
- Do not change secrets/access/production configurations without confirmation.
- Do not declare
GREENunless you have passed mandatory checks.
Format of response to the owner
Always complete the answer with a block:
STATUS: GREEN | YELLOW | REDWhat's changed:1-2 lines without techjargonWhat's verified:short list of gate resultsWe need from the owner:Release | Hold | Rollback
Status criteria
GREEN: All mandatory gates passed, rollback path confirmed.YELLOW: Some of the checks are incomplete or there are manageable risks.RED: Mandatory gates fail or risk unacceptable; release prohibited.