How do I install the Technical Task skill?

Run npx skillmds@latest add nexadevapp/technical-task in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Technical Task safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Technical Task?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Technical Task free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Technical Task?

nexadevapp (@nexadevapp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Technical Task by nexadevapp — Agent Skill

Name: Technical Task
Author: nexadevapp

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.

nexadevapp Updated Sep 21, 2026

File contents

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 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

Read existing technical tasks in docs/technical_tasks/ to determine the next TT-XXX ID
Understand the task to document from the user's request or from a prerequisite discovered during UC implementation
Write the Overview section with category and goal
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.
Define concrete, verifiable acceptance criteria
Identify affected areas of the codebase
List dependencies on other TTs or UCs
Set status to Draft (or Approved if the user confirms)
Create a GitHub tracking issue by following the Before Implementation steps in ${CLAUDE_PLUGIN_ROOT}/shared/tracking/TRACKING.md

---name: technical-taskdescription: 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.---# Technical Task Specification## InstructionsCreate 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 GateRead and follow `${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md`.## TemplateUse [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## Workflow1. Read existing technical tasks in `docs/technical_tasks/` to determine the next TT-XXX ID2. Understand the task to document from the user's request or from a prerequisite discovered during UC implementation3. Write the Overview section with category and goal4. 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 criteria6. Identify affected areas of the codebase7. List dependencies on other TTs or UCs8. 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`

Frequently asked questions