skills.rest
maestria-co
maestria-coOFFICIAL
Explore all skills by this author →
GitHub

asana-story

Format structured story specs into Asana-ready task descriptions with markdown sections.

Updated Mar 2, 2026
Search Tags:#documentation#formatting#story#task#product-management#acceptance-criteria#asana
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill asana-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asana-story
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/asana-story
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill asana-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured story specs often fail to translate cleanly into task management tools, causing inconsistent task definitions and extra manual drafting. This skill formats a structured story spec into a well-formed Asana task, providing a ready-to-use task body and guidance for downstream work.

Core Features & Use Cases

  • Converts a structured story spec (user story, draft acceptance criteria, technical notes, dependencies, and open questions) into an Asana-ready task description.
  • Produces a clear narrative in the task body, including sections for Story, Problem Statement, Acceptance Criteria, and Technical Notes to streamline grooming and handoff.
  • Use Case: a product-manager provides a story spec; the skill outputs a ready-to-create Asana task suitable for sprint planning and progress tracking.

Quick Start

Convert a well-formed story spec into an Asana task description.

Frequently Asked Questions about asana-story

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

FAQPage Schema
How do I convert a user story into an Asana task description?▼

Formatting user stories into Asana-ready tasks requires mapping story specs, acceptance criteria, and technical notes into a structured task body. This skill generates a markdown block containing Task Name, Assignee, Priority, Tags, and a Description section for sprint planning.

What is included in an Asana-ready task description for product management?▼

An Asana-ready task description includes a Task Name, Assignee, Due Date, Priority, and Tags. The Description section contains the Story, Problem Statement, Acceptance Criteria, and Technical Notes to streamline grooming and sprint handoff.

How do I format acceptance criteria and technical notes for Asana tasks?▼

Format acceptance criteria and technical notes by inputting a structured story spec into the skill. It processes the user story, problem statement, criteria, and notes, outputting a well-structured markdown task body ready for Asana.

Do I need a specific format to generate Asana tasks from user stories?▼

You need a structured story spec containing the user story, draft acceptance criteria, technical notes, dependencies, and open questions. The skill uses these inputs to generate a consistent, ready-to-create Asana task description.

Why do structured story specs fail to translate cleanly into task management tools?▼

Structured story specs fail to translate cleanly into task management tools because manual drafting causes inconsistent task definitions. This skill solves the problem by automatically formatting story specs into well-formed Asana task descriptions.

Related Skills

Explore More Product & Management Skills→
maestria-comaestria-co

jira-story

Format structured story specs into Jira-ready user stories with Markdown output.

Official
Intermediate
majunbaomajunbao

feishu-task

Automates Feishu task and task list management including roles and due dates.

Community
Intermediate
fabiolpgomesfabiolpgomes

aiox-sm

Generate structured user stories from PRDs and manage local git branches.

Community
Advanced
uesleinaschuesleinasch

jira-card-maker

Format Jira items with GIVEN/WHEN/THEN acceptance criteria in Brazilian Portuguese.

Community
Advanced