Create and maintain technical documentation including technical specifications, API documentation, system architecture docs, and developer guides.
/plugin marketplace add marcel-Ngan/ai-dev-team/plugin install marcel-ngan-ai-dev-team@marcel-Ngan/ai-dev-teamThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create and maintain technical documentation including technical specifications, API documentation, system architecture docs, and developer guides.
| Tool | Purpose |
|---|---|
Atlassian:createConfluencePage | Create new documentation |
Atlassian:updateConfluencePage | Update existing docs |
Atlassian:getConfluencePage | Read current content |
Atlassian:searchConfluenceUsingCql | Find existing docs |
{
"cloudId": "{{confluence.cloudId}}",
"spaceId": "{{confluence.spaceId}}",
"spaceKey": "{{confluence.spaceKey}}",
"parentPages": {
"technical": "{{confluence.parentPages.technical}}"
}
}
# Technical Specification: {{featureName}}
**Version:** 1.0
**Author:** Software Architect Agent
**Created:** {{date}}
**Status:** Draft | In Review | Approved
**Related:** BRD-{{number}} | EPIC-{{number}}
---
## Overview
### Purpose
[What this specification covers]
### Scope
[What is included/excluded]
### Related Documents
- BRD: [Link]
- ADR: [Link]
---
## Architecture
### System Context
[How this fits in the overall system]
### Component Diagram
┌─────────────┐ ┌─────────────┐ │ Client │────►│ API │ └─────────────┘ └──────┬──────┘ │ ┌──────▼──────┐ │ Service │ └──────┬──────┘ │ ┌──────▼──────┐ │ Database │ └─────────────┘
### Data Flow
1. [Step 1]
2. [Step 2]
3. [Step 3]
---
## Technical Design
### Data Model
#### Entity: {{EntityName}}
| Field | Type | Constraints | Description |
|-------|------|-------------|-------------|
| id | UUID | PK | Unique identifier |
| name | string | NOT NULL | |
| created_at | timestamp | NOT NULL | |
### API Design
#### Endpoint: {{method}} {{path}}
**Request:**
```json
{
"field": "value"
}
Response (200):
{
"id": "uuid",
"field": "value"
}
Error Responses:
| Code | Description |
|---|---|
| 400 | Invalid request |
| 401 | Unauthorized |
| 404 | Not found |
| Component | Technology | Rationale |
|---|---|---|
| Backend | ||
| Database | ||
| Cache |
| Setting | Default | Description |
|---|---|---|
| Metric | Target | Measurement |
|---|---|---|
| Response time | <200ms | P95 |
| Throughput | 1000 RPS |
### Create Tech Spec Example
```javascript
Atlassian:createConfluencePage({
cloudId: "{{confluence.cloudId}}",
spaceId: "{{confluence.spaceId}}",
parentId: "{{confluence.parentPages.technical}}",
title: "Tech Spec: User Authentication",
body: `# Technical Specification: User Authentication
**Version:** 1.0
**Author:** Software Architect Agent
**Created:** 2025-01-06
**Status:** Draft
**Related:** BRD-001 | MDDEV-100
---
## Overview
### Purpose
Define the technical implementation for user authentication including registration, login, and session management.
### Scope
- User registration and validation
- Password hashing and storage
- JWT-based authentication
- Session management
---
## Architecture
### Component Diagram
\`\`\`
┌─────────────┐ ┌─────────────┐
│ Client │────►│ Auth API │
└─────────────┘ └──────┬──────┘
│
┌──────▼──────┐
│ Auth Service│
└──────┬──────┘
│
┌──────▼──────┐
│ User DB │
└─────────────┘
\`\`\`
---
## Technical Design
### Data Model
#### Entity: User
| Field | Type | Constraints | Description |
|-------|------|-------------|-------------|
| id | UUID | PK | Unique identifier |
| email | string | UNIQUE, NOT NULL | User email |
| password_hash | string | NOT NULL | Bcrypt hash |
| created_at | timestamp | NOT NULL | Registration date |
### API Design
#### POST /auth/register
**Request:**
\`\`\`json
{
"email": "user@example.com",
"password": "securePassword123"
}
\`\`\`
**Response (201):**
\`\`\`json
{
"id": "uuid",
"email": "user@example.com"
}
\`\`\`
---
## Security Considerations
- Passwords hashed with bcrypt (cost factor 12)
- JWT tokens expire after 24 hours
- Rate limiting on auth endpoints
- HTTPS required
`,
contentFormat: "markdown"
})
# API Documentation: {{serviceName}}
**Base URL:** `{{baseUrl}}`
**Version:** v1
**Last Updated:** {{date}}
---
## Authentication
All endpoints require Bearer token:
Authorization: Bearer <token>
---
## Endpoints
### {{Resource}}
#### List {{Resources}}
`GET /{{resources}}`
**Query Parameters:**
| Param | Type | Required | Description |
|-------|------|----------|-------------|
| page | int | No | Page number |
| limit | int | No | Items per page |
**Response:**
```json
{
"data": [...],
"pagination": {
"page": 1,
"total": 100
}
}
GET /{{resources}}/:id
POST /{{resources}}
PUT /{{resources}}/:id
DELETE /{{resources}}/:id
| Code | Message | Description |
|---|---|---|
| 400 | Bad Request | Invalid input |
| 401 | Unauthorized | Missing/invalid token |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource not found |
| 500 | Server Error | Internal error |
---
## Used By Agents
| Agent | Document Types |
|-------|---------------|
| **Software Architect** | Tech Specs, Architecture Docs |
| **Senior Developer** | API Docs, Implementation Guides |
| **DevOps Engineer** | Infrastructure Docs |
## Error Handling
| Error | Cause | Resolution |
|-------|-------|------------|
| 400 Bad Request | Invalid markdown/code blocks | Escape special characters |
| 404 Not Found | Parent page missing | Create parent first |
| 413 Too Large | Document too big | Split into multiple pages |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.