# Structure Collaborative Coding Work

AI coding sessions can drift without shared process, security checks, and clear decision points. This skill gives Claude, Codex, and Claude Code a practical framework for collaborative, production-minded development.

## Install

```bash
npx skillstore add backgwa/agentic-structure
```

## Metadata

- - Slug: backgwa-agentic-structure
- - Version: 1.0.0
- - Author: BackGwa
- - GitHub username: BackGwa
- - License: MIT
- - Repository: https://github.com/BackGwa/Agentic-Structure/tree/main/plugins/skills/agentic-structure
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: network, filesystem
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/backgwa-agentic-structure
- - Manifest: https://skillstore.pages.dev/api/skills/backgwa-agentic-structure/manifest

## Capabilities

- Selects relevant development guidelines for planning, coding, comments, errors, security, and knowledge gaps.
- Encourages core logic before integration and interface work.
- Provides security defaults for secrets, hashing, authorization, rate limits, uploads, and production exposure.
- Defines when to ask users for decisions, missing requirements, or domain knowledge.
- Guides high-signal comments and consistent error handling across layers.
- Documents external references when technical information must be preserved.

## Use Cases

- Plan a New Feature Safely: Break a feature into core logic, integration, and interface steps before implementation starts.
- Standardize AI Coding Reviews: Use shared criteria for security, error handling, comments, and maintainability during code review.
- Manage Unknown Requirements: Identify knowledge gaps, ask focused questions, and document references before coding speculative behavior.

## Prompt Templates

### Start With Structure

```
Use agentic-structure to plan this feature. Identify core logic, integration work, interface work, risks, and validation steps.
```

### Review Code Quality

```
Apply agentic-structure to review this change for maintainability, comments, error handling, and security assumptions.
```

### Resolve Ambiguity

```
Use agentic-structure to identify unclear requirements, present two or three implementation options, and recommend one with reasoning.
```

### Audit a Production Path

```
Apply agentic-structure to evaluate this production workflow for secrets handling, authorization, rate limits, failure modes, and validation coverage.
```

## Limitations

- It is a guidance-only skill and does not implement code by itself.
- It may require user input when requirements or architecture choices are unclear.
- Its file and web reference workflow depends on tool permissions in the host agent.
- It does not replace project-specific security review or tests.

## Best Practices

- Use the guideline selection matrix before starting broad coding tasks.
- Run validation after each logical implementation step.
- Document security assumptions when code cannot express them clearly.

## Anti Patterns

- Do not treat the guidelines as a substitute for project requirements.
- Do not create reference files for information already visible in the codebase.
- Do not use broad error handling that hides useful failure context.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T13:12:23.312\+00:00
- - Summary: Static analysis reported many critical and high patterns, but review found them to be documentation false positives, mostly Markdown backticks, security terminology, and examples that warn against unsafe practices. No prompt injection, credential access, malware behavior, or command execution intent was found. The remaining low risk is that the knowledge protocol describes creating reference files and using web fetches for documentation.

## Stats

- - Views: 226
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0