# Adapt AI Responses with Behavioral Modes

General-purpose assistants can use the wrong approach for a task. This skill selects structured modes for ideation, implementation, debugging, review, teaching, release, and collaboration.

## Install

```bash
npx skillstore add sickn33/behavioral-modes
```

## Metadata

- Status: approved
- Slug: sickn33-behavioral-modes
- Skillstore revision: r2
- Version status: missing
- Tree hash: fea3da2ca58a37c452896446ad44ae576a3007c9b0c65e33746b10844a0ba2af
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/behavioral-modes
- Ref: 5a26d1d61d694db29af9b138c661c1981076d9df
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-behavioral-modes
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-behavioral-modes/manifest

## Capabilities

- Selects a mode from task signals such as build, debug, review, explain, or deploy.
- Defines focused behavior and output formats for six primary operating modes.
- Supports explicit mode selection through short slash-prefixed requests.
- Provides an explore, plan, execute, and critique pattern for complex work.
- Structures release checks across code quality, security, and performance.

## Use Cases

- Plan a Product Feature: Compare several approaches before choosing architecture or implementation details.
- Resolve a Software Defect: Organize symptoms, root cause analysis, fixes, and prevention steps.
- Prepare a Production Release: Review stability, security, quality, and performance before deployment.

## Prompt Templates

### Choose a Mode

```
Choose the best behavioral mode for this task: [task]. State the mode and begin with its expected structure.
```

### Brainstorm Alternatives

```
Use BRAINSTORM mode for [goal]. Present at least three options with benefits, drawbacks, and one decision question.
```

### Debug a Reproducible Issue

```
Use DEBUG mode. Analyze this symptom: [symptom]. Reproduction steps: [steps]. Evidence: [logs]. Identify the root cause, fix, and prevention.
```

### Coordinate Complex Delivery

```
Use EXPLORE and PLAN-EXECUTE-CRITIC modes for [project]. Map dependencies, define atomic tasks, implement each task, then review security and performance.
```

## Limitations

- Mode selection depends on clear task wording and may require user clarification.
- The skill provides behavior guidance but does not supply domain-specific implementation knowledge.
- Release checklists do not replace project tests, deployment controls, or expert review.
- Referenced skills and artifacts may not exist in every assistant environment.

## Best Practices

- Provide the task goal, constraints, and expected outcome before selecting a mode.
- Use one primary mode and add another only when the workflow clearly changes.
- Validate generated work with project-specific tests, policies, and human review.

## Anti Patterns

- Do not force implementation mode when requirements or constraints remain unclear.
- Do not treat a formatted checklist as proof that validation was completed.
- Do not combine many modes without defining their order and responsibilities.

## Security Audit

- Audited at: 2026-08-14T10:21:45.665\+00:00
- Summary: All static alerts are false positives caused by Markdown fences, inline code formatting, filenames, or ordinary instructional text. The skill contains no executable shell logic, system reconnaissance, prompt injection, or other semantic security issue.

## Stats

- Views: 91
- Downloads: 11
- Favorites: 0
- Popularity score: 0