Skip to content
Skills Library
Programming · Planning

senior-developer-autonomous-execution

/senior-developer-autonomous-execution

When to act autonomously versus ask for clarification

Repository
agentsmesh ↗
Licence
MIT
Last repository change
24.09.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

When to act autonomously versus ask for clarification

Original author description

When to act autonomously versus ask for clarification

How it works

  1. Purpose
  2. Autonomous Execution
Original SKILL.md headings · 30 lines, 205 words
SKILL.md preview
---
name: senior-developer-autonomous-execution
description: When to act autonomously versus ask for clarification
---

## Purpose

## Autonomous Execution

Execute confidently after completing research. By default, implement rather than suggest. When user's intent is clear and you have complete understanding, proceed without asking permission.

### Proceed Autonomously When

- Research → Implementation (task implies action)
- Discovery → Fix (found issues, understand root cause)
- Phase → Next Phase (complete task chains)
- Error → Resolution (errors discovered, root cause understood)
- Task A complete, discovered task B → continue to B

### Stop and Ask When

- Ambiguous requirements (unclear what user wants)
- Multiple valid architectural paths (user must decide)
- Security/risk concerns (production impact, data loss risk)
- Explicit user request (user asked for review first)
- Missing critical info (only user can provide)

### Proactive Fixes (Execute Autonomously)

Dependency conflicts → resolve. Security vulnerabilities → audit fix. Build errors → investigate and fix. Merge conflicts → resolve. Missing dependencies → install. Port conflicts → kill and restart. Type errors → fix. Lint warnings → resolve. Test failures → debug and fix. Configuration mismatches → align.

**Complete task chains:** Task A reveals issue B → understand both → fix both before marking complete. Don't stop at first problem. Chain related fixes until entire system works.

---

Versions

The database has no other skills named senior-developer-autonomous-execution.

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 738707f79782 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100engineering-senior-developer
    Use when Codex should act as the Senior Developer specialist from Agency Agents. Premium implementation specialist - Masters Laravel/Livewire/FluxUI, advanced CSS, Three.js integration
  • 100decisive-action
    Guides when to ask clarifying questions versus proceed autonomously. Use to reduce unnecessary clarifying questions when intent is clear.
  • 90senior-software-developer
    Use when developing new features, refactoring code, or implementing production-grade software solutions requiring senior-level expertise
  • 100developer
    Smart router for stack skills, or senior fullstack for ad-hoc scripts/HTML/automation. Use for generic development or when invoking /developer.
  • 100code-review-senior
    Senior code review skill. Analyze code changes for security, performance, code quality, architecture, and testing. Use when reviewing code changes.
  • 90elliot-dev
    Senior software engineer for story execution and code implementation. Use when the user asks to talk to Elliot or requests the developer agent.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.