Can I customize the output language of the tasks?

Yes, the skill checks the 'language' field in your project's aico.json root file to determine the output language, defaulting to English if unset.

Does it include testing in the task breakdown?

Yes, creating unit, integration, and API tests is a mandatory final layer in every task breakdown generated by this skill.

Where does the skill store the generated task lists?

All task files are automatically saved to the docs/reference/backend/tasks/ directory, named after the specific story being processed.

What architectural pattern does this skill follow?

It follows a strict layered architecture: Data Models, Database Migrations, Repository Layer, Service Layer, API Layer, Validation, and finally Tests.

Layered Backend Task Architect

Name: Layered Backend Task Architect
Author: yellinzero

byyellinzero

API Development

Transforms product stories into structured backend implementation tasks following strict layered architecture principles.

About

This skill automates the transition from product requirements to implementation by breaking down project stories into a logical sequence of backend tasks. By enforcing a strict architectural order—moving from data models and migrations through to API endpoints and tests—it ensures developers have a clear, dependency-aware roadmap that maintains separation of concerns and technical consistency across the entire backend stack.

Key Features

Automatic dependency mapping between implementation steps
Strict layered architecture task ordering (Data → Repository → API → Tests)
Integrated validation and error handling task generation
0 GitHub stars
Multi-language support driven by project configuration
Standardized documentation output to project-specific task directories

Use Cases

Initializing new feature development with pre-defined, testable technical milestones
Converting a PRD or user story into a granular backend development plan
Standardizing implementation steps across a team to ensure architectural consistency

About

Key Features

Automatic dependency mapping between implementation steps
Strict layered architecture task ordering (Data → Repository → API → Tests)
Integrated validation and error handling task generation
0 GitHub stars
Multi-language support driven by project configuration
Standardized documentation output to project-specific task directories

Use Cases

Initializing new feature development with pre-defined, testable technical milestones
Converting a PRD or user story into a granular backend development plan
Standardizing implementation steps across a team to ensure architectural consistency