assemble

Generate YAML team manifests with roles, responsibilities, and file ownership.

14|6|Updated Feb 3, 2026

Search Tags:#workflow automation #project setup #team #persistent learning #agent roles #team manifest

Ready to run

npx skills add https://github.com/tyevans/tackline --skill assemble

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assemble
Source: https://github.com/tyevans/tackline/tree/main/skills/teams/assemble
Command: npx skills add https://github.com/tyevans/tackline --skill assemble

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of persistent, specialized agent teams for projects, ensuring knowledge accumulation and role clarity across multiple work sessions.

Core Features & Use Cases

Team Creation: Define roles, responsibilities, and file ownership for project agents.
Persistent Learning: Agents accumulate knowledge in dedicated files, improving performance over time.
Structured Workflow: Guides users through project understanding, role proposal, and team manifest generation.
Use Case: Kickstart a new software project by defining distinct roles like 'architect', 'backend', and 'frontend', each with clear ownership and a dedicated learning file.

Quick Start

Use the assemble skill to set up a new project team with the description "A new e-commerce platform".

Frequently Asked Questions about assemble

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

FAQPage Schema

How do I set up persistent agent teams for long-horizon projects?▼

To set up persistent agent teams, you define project roles, responsibilities, and file ownership. This Skill generates YAML manifests and per-member learning files to facilitate structured team coordination and knowledge accumulation across multiple sessions.

What is the best way to maintain agent role clarity and knowledge across multiple work sessions?▼

Maintaining agent role clarity across sessions requires persistent learning files where agents accumulate knowledge. This approach ensures specialized agents retain project understanding and improve performance over time without losing context between work intervals.

How do I define file ownership and responsibilities for an automated project workflow?▼

Defining file ownership involves guiding the project understanding phase, proposing roles, and generating a team manifest. You can provide a project description interactively or through arguments to refine the proposed team structure with clear ownership boundaries.

Can I kickstart a new software project team by providing a simple text description?▼

Yes, you can kickstart a new software project team using a simple description. The Skill supports interactive or argument-driven project description input to automatically propose and refine distinct team structures like architect, backend, and frontend roles.

Does generating a team manifest require manually writing YAML files?▼

Generating a team manifest does not require manually writing YAML files. The Skill automatically produces the YAML manifest and dedicated per-member learning files based on the proposed team structure and project description you provide.