Run any Skill in Manus with one click

autonomous-dev-planning

Stars1

Forks0

UpdatedJune 21, 2026 at 11:49

Use when starting autonomous development on a feature, bug fix, or refactor. Performs deep codebase research, dependency analysis, and creates a structured implementation plan without writing any code. Designed for token-efficient autonomous workflows.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aj1126

aj1126/antigravity-token-optimizations

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	autonomous-dev-planning
description	Use when starting autonomous development on a feature, bug fix, or refactor. Performs deep codebase research, dependency analysis, and creates a structured implementation plan without writing any code. Designed for token-efficient autonomous workflows.

Autonomous Development - Planning

Prepare an implementation plan for autonomous execution.

CRITICAL CONSTRAINT: RESEARCH & PLANNING ONLY

Do not modify files or run test/build commands. Sole output is implementation_plan.md. Every token must reduce execution risk.

Instructions

Reconnaissance: Identify affected modules, map dependencies, find existing tests and conventions.
Impact: List all files to create/modify/delete, flag risks/regressions, clarify ambiguities, estimate unit complexity.
Sequence: Order atomic, verifiable steps. Define functions/API contracts.
Verification: List exact test commands and acceptance criteria.

Output Format

Create implementation_plan.md using the standard format. Keep descriptions/bullets <10 words. Request feedback.

More from this repository

same repository

workspace-onboarding-review

aj1126/antigravity-token-optimizations

Use to audit, evaluate, and verify workspace configuration compliance and inheritance integrity against universal workstation standards.

2026-06-211

workspace-onboarding-development

aj1126/antigravity-token-optimizations

Use to execute the implementation phase of onboarding an existing project workspace. Generates localized overrides, configuration snippets, and pre-commit hooks.

2026-06-211

workspace-onboarding-planning

aj1126/antigravity-token-optimizations

Use when onboarding an existing project workspace into our hierarchical workstation ecosystem. This skill performs gap analysis, local override mapping, and refactoring planning without generating code.

2026-06-211

git-check-commit-push

aj1126/antigravity-token-optimizations

Check for untracked/modified changes in the workspace, draft a descriptive commit message, commit them, and push the commit.

2026-06-211

document-driven-design-only

aj1126/antigravity-token-optimizations

Run the research and planning phase of development to produce a functional architecture, design spec, and checklist without modifying code or writing implementation files.

2026-06-211

document-driven-design

aj1126/antigravity-token-optimizations

Provides a structured workflow for Document-Driven Design (DocDD) and development. Guides the agent to design functional architectures, identify technical pitfalls, and write token-efficient specs suitable for local models (e.g. Ollama) before coding.

2026-06-211

name	autonomous-dev-planning
description	Use when starting autonomous development on a feature, bug fix, or refactor. Performs deep codebase research, dependency analysis, and creates a structured implementation plan without writing any code. Designed for token-efficient autonomous workflows.

Autonomous Development - Planning

Prepare an implementation plan for autonomous execution.

CRITICAL CONSTRAINT: RESEARCH & PLANNING ONLY

Do not modify files or run test/build commands. Sole output is implementation_plan.md. Every token must reduce execution risk.

Instructions

Reconnaissance: Identify affected modules, map dependencies, find existing tests and conventions.
Impact: List all files to create/modify/delete, flag risks/regressions, clarify ambiguities, estimate unit complexity.
Sequence: Order atomic, verifiable steps. Define functions/API contracts.
Verification: List exact test commands and acceptance criteria.

Output Format

Create implementation_plan.md using the standard format. Keep descriptions/bullets <10 words. Request feedback.