# Technical Task

> Creates technical task specification documents for engineering work that has no user-facing scenario: configuration, cleanup, dependency updates, infrastructure, and developer experience improvements. Use when the user asks to "create a technical task", "set up the database", "bump a dependency", "add a dev profile", "clean up code", or mentions infrastructure tasks, configuration changes, or maintenance work.

- Skill: `nexadevapp/technical-task` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add nexadevapp/technical-task`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nexadevapp/technical-task/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: nexadevapp (https://skillmd.com/u/nexadevapp)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/nexadevapp/technical-task

---


# Technical Task Specification

## Instructions

Create or update technical task specification documents for $ARGUMENTS in `docs/technical_tasks/`. Each technical task describes engineering work that does not correspond to a use case.

## DO NOT

- Write vague or unmeasurable acceptance criteria
- Mix multiple unrelated tasks in one document
- Use a technical task for work that has user-facing scenarios (use a use case instead)

## Nexa Rules Gate

Read and follow `${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md`.

## Template

Use [templates/technical-task.md](templates/technical-task.md) as the document structure.

## Example Technical Task

# Technical Task: Set Up Dev Profile

## Overview

| | |
|---|---|
| **Task ID** | TT-001 |
| **Task Name** | Set Up Dev Profile |
| **Category** | Configuration |
| **Goal** | Create a development profile with seed data and relaxed security so developers can run the application locally without external dependencies. |
| **Scope** | Umbrella |
| **Status** | Approved |

## Acceptance Criteria

- [ ] A dev profile exists that starts the application with an in-memory or local database
- [ ] Seed data is loaded automatically when the dev profile is active
- [ ] The application starts successfully with the dev profile and no external services
- [ ] README documents how to activate the dev profile

## Affected Areas

- Application configuration files
- Database seed scripts
- README.md

## Dependencies

- None

## Workflow

1. Read existing technical tasks in `docs/technical_tasks/` to determine the next TT-XXX ID
2. Understand the task to document from the user's request or from a prerequisite discovered during UC implementation
3. Write the Overview section with category and goal
4. Set **Scope** — `Cluster: <name>` when the task supports exactly one cluster from
   `docs/engineering/progress.md`, `Umbrella` when it is cross-cutting. The project
   overview groups technical tasks by this field.
5. Define concrete, verifiable acceptance criteria
6. Identify affected areas of the codebase
7. List dependencies on other TTs or UCs
8. Set status to Draft (or Approved if the user confirms)
9. Create a GitHub tracking issue by following the **Before Implementation** steps in `${CLAUDE_PLUGIN_ROOT}/shared/tracking/TRACKING.md`