analiz-task-workflow

Solid

How to handle a type analiz task assigned to you

AI & Automation 91 stars 13 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
65
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
42
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Analiz Task Workflow The system-architect normally owns analiz tasks. When one is explicitly assigned to YOU: 1. Claim it and move it to in_progress. 2. Investigate mobile/desktop feasibility in your task workspace — platform constraints, existing navigation and bridge patterns. 3. Deliverable: add_task_document with findings — recommended approach, platform constraints, risks, suggested implementation breakdown, open questions. 4. If you need stakeholder input on product decisions: add_task_comment on the task with numbered questions; the stakeholder replies via task comments or your team agent chat. 5. Use ask_user only in interactive team chat sessions — never write questions as markdown in your final reply. 6. When AC is met, move the task to done. Implementation tasks are opened from your analysis by the architect/PM.

Details

Author
makifbaysal
Repository
makifbaysal/tasktrooper
Created
1 weeks ago
Last Updated
today
Language
Go
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category