add-task-type

Generate standardized task-type definitions with description.json and instruction.md for ARF projects.

16|8|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GliteTech/glite-arf --skill add-task-type
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-task-type
Source: https://github.com/GliteTech/glite-arf/tree/main/arf/skills/add-task-type
Command: npx skills add https://github.com/GliteTech/glite-arf --skill add-task-type

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of standardized task-types for ARF projects, reducing manual setup and ensuring consistency across tasks.

Core Features & Use Cases

  • Interactive dialogue to propose and confirm task-type candidates based on the project description.
  • Automatically generate description.json and instruction.md for each accepted task type.
  • Verifies with the built-in verificator to ensure compliance with the specification before commit.

Quick Start

Start the skill to propose and create task types from your project description.

Frequently Asked Questions about add-task-type

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create standardized task types for an ARF project?

The skill generates standardized task types by interactively proposing candidates from your project description, then creating description.json and instruction.md files validated by a built-in verificator.

What files are generated when setting up task types interactively?

Setting up task types interactively generates a description.json and an instruction.md file for each accepted task type, ensuring all definitions comply with the ARF task_type_specification.md before commit.

Do I need an existing project description to automate task-type definitions?

Yes, you need an existing project/description.md. The skill reads this file to propose and confirm task-type candidates that align with your recurring workflows and project setup requirements.

How does the verificator ensure task-type specifications are compliant?

The verificator checks generated task-type definitions against arf/specifications/task_type_specification.md and existing styleguides, ensuring only validated files are committed to your project's meta/task_types directory.

Can I use this for recurring workflows in project setup?

Yes, this targets project setup and recurring workflows. It reads existing meta/task_types and project descriptions to interactively select and define standardized task types for your ARF projects.