cf-project

Decompose large specifications into structured projects, subprojects, and tickets.

2|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fimmtiu/code-factory --skill cf-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-project
Source: https://github.com/fimmtiu/code-factory/tree/main/skills/cf-project
Command: npx skills add https://github.com/fimmtiu/code-factory --skill cf-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates turning a large specification into a structured set of Code Factory projects, each with detailed tickets for parallel implementation.

Core Features & Use Cases

  • Breaks down a specification into a top-level project, subprojects, and tickets with clear identifiers.
  • Automated guidance for dependencies, write scopes, and PRD content to enable parallel workstreams.
  • Useful for planning large initiatives that involve multiple teams and ticket types (projects, subprojects, tickets).

Quick Start

Create a specification and tell the system to decompose it into a top-level project, nested subprojects, and a full set of tickets.

Frequently Asked Questions about cf-project

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

FAQPage Schema
How do I decompose a large software specification into parallel workstreams?

Project decomposition breaks a large specification into a structured tree of top-level projects, nested subprojects, and detailed tickets for parallel implementation across multiple teams.

How do I generate actionable tickets with dependencies for complex project management?

Generating actionable tickets involves automated guidance for mapping dependencies, defining write scopes, and embedding PRD content to enable parallel implementation across multiple teams.

What is the best way to structure large initiatives into subprojects and tickets for multiple teams?

The best way to structure large initiatives is to create a top-level project, nest subprojects within it, and generate a full set of detailed tickets equipped with metadata and PRD content for parallel execution.

Can I use automated ticketing to map write scopes and dependencies across parallel implementation teams?

Yes, automated ticketing applies to complex initiatives by providing clear identifiers, mapping dependencies, and defining write scopes to facilitate parallel workstreams across multiple teams.

When do I need structured project decomposition for software engineering initiatives?

You need structured project decomposition when managing complex software engineering initiatives that require turning a large specification into clear identifiers, dependencies, and parallel workstreams across multiple teams.