Bind a flow workspace to wherever the work is actually managed — GitHub Issues and Projects, Jira, Linear, an internal Kanban dashboard, a spreadsheet, or chat — by choosing a system-of-record mode (files-only, mirror, adopt, split), writing a field-ownership map with exactly one writer per field, and using the board export plus the harness's own tools to sync. Use when leadership needs the flow where they already look, when a tracker already holds the work, or when a sync has started fighting the workspace. Part of the flow-driven family.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
This skill hasn't been evaluated yet
tessl scenario generatetessl eval runyyeret/portfolio-pdlc
cb337f8
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.