Task writer

Skill imamirezaei/Product-Team-Claude-Skills/policy/product-manager/skills/task-writer

Use when writing a task or issue for the team. Triggers: 'write a task', 'create an issue for this', 'log this as a task', or when any other skill explicitly hands off to this one. Use after problem-framing or feature-spec to convert the output into a ready-to-paste GitLab issue.From its SKILL.md

Install

npx -y skills add imamirezaei/Product-Team-Claude-Skills --skill task-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 480 tokens by cl100k_base, as published. Nobody here has run it

Task Writer

Read the working-language field from CLAUDE.md and deliver all output in that language. Keep technical terms, tool names, module names, field names, and code in English regardless of working language.

Title

Write the title using the Conventional Commits format:

type(scope): short imperative description

Types:

Type	When to use
`feat`	New feature or capability
`fix`	Bug fix or incorrect behavior
`refactor`	Code change with no behavior change
`perf`	Performance improvement
`chore`	Maintenance, dependency update, tooling
`docs`	Documentation only
`test`	Adding or fixing tests
`style`	UI/visual change with no logic change
`ci`	CI/CD pipeline change

Scope is optional but recommended — use the affected module, feature area, or team (e.g. auth, dashboard, api, onboarding).

Examples:

feat(onboarding): add email verification step
fix(auth): redirect to login on session expiry
refactor(dashboard): extract chart component
chore(deps): upgrade Vue to 3.5

Body

🧢 Task Description [What needs to be done and why. One short paragraph.]

🦣 User Story As a [user type], I want [goal], so that [outcome].

🧱 Implementation Notes [Technical notes, dependencies, and constraints the team should know. Reference findings from feature-dependency or design-system-check if available.]

✅ DOD ✓ [Testable item 1] ✓ [Testable item 2] ✓ [Testable item 3]

❌ Out of scope:

[Item 1]

Constraints

DOD items must be testable — if an item cannot be verified, rewrite it
Out of scope must be explicit — silence is not the same as exclusion
Implementation Notes should contain information for the team, not a restatement of the user story
Title must follow Conventional Commits exactly — no free-form titles

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.