ferran-task

Name: ferran-task
Availability: InStock
Author: ferranguardia

Create standardized task files with context, scope, and acceptance criteria.

Updated Mar 2, 2026

Search Tags:#automation #validation #task #project-management #agent-workflow #task-file

Ready to run

npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill ferran-task

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ferran-task
Source: https://github.com/FerranGuardia/claude-autonomous-setup/tree/main/global/skills/ferran-task
Command: npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill ferran-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes task work by creating well-formed task files that capture context, scope, and acceptance criteria.

Core Features & Use Cases

Standard Task Template: Ensures status, tracking, dependencies, and validation are included in every task.
Validation & Evidence: Each task includes verifiable criteria and an index to update progress.
Project Convention Adherence: Guides the user to consult CLAUDE.md for prefixes, tracking files, and locations.
Completion Protocol: Defines how to mark tasks DONE with evidence.

Quick Start

In your project workspace, run /ferran-task new to generate a new task file that follows the project conventions.

Frequently Asked Questions about ferran-task

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

FAQPage Schema

How do I create structured task files for agent workflows?▼

To create structured task files for agent workflows, use a standardized task template that captures context, scope, and acceptance criteria while enforcing status tracking and validation evidence. This ensures every task file follows consistent project conventions and includes verifiable completion protocols.

What should a project task template include for tracking and validation?▼

A project task template should include status fields, tracking references, dependency lists, and verifiable acceptance criteria. It must also define a completion protocol that requires evidence before marking a task as done, ensuring structured validation and explicit progress tracking throughout the workflow.

Does this task file generation approach work with custom project conventions?▼

Yes, this task file generation approach works with custom project conventions by consulting your project's configuration file for naming prefixes, tracking file locations, and directory structures. The generated task files adhere to your specific project rules rather than imposing a rigid external format.

What is the best way to enforce a completion protocol for project tasks?▼

The best way to enforce a completion protocol for project tasks is to define a structured workflow that requires explicit evidence and status updates before marking a task as done. This validation step ensures accountability and tracks progress within an index of project tasks.

Can I use these structured task files for end-to-end testing workflows?▼

Yes, you can use these structured task files for end-to-end testing workflows. The standardized task template integrates with broader agent workflow series, capturing the necessary scope and acceptance criteria required to validate and track complex end-to-end testing procedures.