folio

Manage knowledge work lifecycles with structured planning, composition, and publishing workflows.

3|1|Updated Nov 5, 2022

Search Tags:#planning #project management #publishing #composition #lifecycle #knowledge work

Ready to run

npx skills add https://github.com/thebrokencube/files-with-a-dot --skill folio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: folio
Source: https://github.com/thebrokencube/files-with-a-dot/tree/main/cmd/folio/skill
Command: npx skills add https://github.com/thebrokencube/files-with-a-dot --skill folio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire knowledge work lifecycle, from initial observation and planning to composition, publishing, and review, ensuring projects are managed efficiently and effectively.

Core Features & Use Cases

Lifecycle Management: Guides projects through observation, spike, design, plan, implementation, and retro stages.
Automated Composition & Publishing: Composes source materials into various targets and publishes them to external systems like Jira and Google Docs.
Use Case: Kickstart a new feature development by using /folio plan to diverge-converge on a design, then /folio compose to assemble documentation, and finally /folio publish to create Jira tickets.

Quick Start

Use the folio skill to list your active projects.

Frequently Asked Questions about folio

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

FAQPage Schema

How do I manage the project lifecycle from planning to publishing documentation?▼

Project lifecycle management from planning to publishing is handled through structured workflows that guide projects through observation, spike, design, plan, implementation, and retro stages. It supports multi-agent planning and automated composition of sources into targets.

Can I publish project artifacts directly to Jira and Google Docs?▼

Publishing project artifacts directly to Jira and Google Docs is supported via defined tooling. The publishing stage takes composed source materials and integrates them into these external systems to finalize the knowledge work lifecycle.

What is the best way to structure knowledge work for feature development?▼

The best way to structure knowledge work for feature development is using a diverge-converge workflow. You can initiate this by planning a design, composing the assembled documentation, and finally publishing the results to create actionable tickets.

Does project management workflow require review gates and materialization invariants?▼

Project management workflows require adherence to materialization invariants and review gates. These constraints ensure robust project execution by enforcing validation checks before advancing through the lifecycle stages.

How do I compose source materials into different project targets?▼

Composing source materials into targets is achieved through an automated composition process. This functionality assembles various input sources into desired output formats as part of the structured project artifact workflow.

Can I use multi-agent planning for project design and knowledge work?▼

Multi-agent planning is supported for project design and knowledge work. The workflow utilizes a diverge-converge approach during the planning stage to effectively structure and refine the design process.