skills.rest
hoshiyar-singh8
hoshiyar-singh8COMMUNITY
Explore all skills by this author →
GitHub

task-decomposition-rules

Decompose iOS feature work into single-layer tasks across VIPER/MVVM, API, DI, and UI flows.

Updated Mar 16, 2026
Search Tags:#planning#architecture#decomposition#ios#tickets#task-splitting
One-click install
npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill task-decomposition-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-decomposition-rules
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/task-decomposition-rules
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill task-decomposition-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Split work into single-layer tasks across VIPER/MVVM, API, DI, and UI flows to simplify planning, auditing, and delivery of iOS features.

Core Features & Use Cases

  • Provides a repeatable framework to decompose work into isolated, single-layer tasks.
  • Defines a common Layer Set with fields such as ui, viewmodel, api, mapper, presenter, interactor, router, navigation, config, test, integration, domain, model, builder, di.
  • Includes patterns for Multi-Surface Flows and Vertical Slices to group tasks effectively.

Quick Start

Create one or more tasks per feature using the single-layer rules above, then connect them with a final wiring task if needed.

Frequently Asked Questions about task-decomposition-rules

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

FAQPage Schema
How do I decompose iOS feature work into single-layer tasks?▼

Single-layer task decomposition splits product work across VIPER/MVVM, API, DI, and UI flows using a defined Layer Set. This enforces strict layer boundaries and prerequisites for each ticket, simplifying planning and delivery.

What is the best way to split complex tickets across VIPER and MVVM layers?▼

Splitting complex tickets across VIPER and MVVM involves isolating tasks into specific layers like viewmodel, interactor, router, and mapper. This ensures each ticket has clear scope boundaries and defined prerequisites before wiring.

Can I use these task-splitting rules for multi-surface flows and vertical slices?▼

Yes, these task-splitting rules support multi-surface flows and vertical slices by grouping isolated single-layer tasks effectively. You create one or more tasks per feature and connect them with a final wiring task.

When do I need a final wiring task during task decomposition?▼

A final wiring task is needed during task decomposition when multiple isolated single-layer tasks must be connected to complete an iOS feature. This ensures all VIPER/MVVM layers, API, and DI flows are properly integrated.

Does this task decomposition framework support dependency injection and UI flow configuration?▼

Yes, this task decomposition framework supports dependency injection and UI flow configuration by including di, builder, config, and navigation within its common Layer Set. This guarantees all architectural components are properly scoped.

Related Skills

Explore More Software Engineering Skills→
quan0715quan0715
31

qjudge-architecture-owner

Define and enforce QJudge layer boundaries, import direction, and file naming conventions.

Community
Intermediate
BryceRoberts13BryceRoberts13

subagent-driven-development

Dispatch subagents for isolated tasks with two-stage spec and code reviews.

Community
Advanced
dagbadagba
3

programmatic-uikit-layout

Build programmatic UIKit layouts using anchor-based Auto Layout.

Community
Advanced
w95w95
145

sprint-planning

Facilitate agile sprint planning with estimation, capacity, and goal frameworks.

Community
Advanced