ワンクリックでManusで任意のスキルを実行

linear-pickup

Scan the Linear Landscaper project for the next available issue to work on. Checks Todo items by priority, verifies dependencies are met, claims the issue, and reports what to do next. Use when an agent needs to find work or the user says "pick up work", "what's next", or "/linear-pickup".

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/Desgue/landscaper --skill linear-pickup

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

Desgue/landscaper

スター0

フォーク0

更新日2026年4月8日 17:12

SKILL.md

readonly

name	linear-pickup
description	Scan the Linear Landscaper project for the next available issue to work on. Checks Todo items by priority, verifies dependencies are met, claims the issue, and reports what to do next. Use when an agent needs to find work or the user says "pick up work", "what's next", or "/linear-pickup".
allowed-tools	["Read","Grep","Glob","Bash(git:*)"]
argument-hint	[optional: label filter e.g. Bug, Spike]

Pick Up Work from Linear

Find the next issue to work on in the Landscaper project.

Context

Team: Engineering (ENG)
Project: Landscaper
Workflow doc: docs/LINEAR-WORKFLOW.md
Description templates: docs/plans/PLAN_TEMPLATE.md

Process

1. Scan Todo issues

Use mcp__linear-server__list_issues to find issues:

Filter: state: "Todo", project: "Landscaper"
If $ARGUMENTS is provided, also filter by label name matching $ARGUMENTS
Sort by priority (Urgent=1 first, then High=2, Medium=3, Low=4)

2. Check dependencies

For each candidate issue (highest priority first):

Use mcp__linear-server__get_issue to read full details
Check the blockedBy field — if any blocking issue is NOT in "Done" state, skip this issue
Check if the issue has a blocker label — if yes, skip

3. Claim the issue

Once a valid issue is found:

Use mcp__linear-server__save_issue to set state: "In Progress"
Use mcp__linear-server__save_comment to post: "Taking this."
If the issue has no estimate, add one (1=small, 3=medium, 5=large based on description complexity)

4. Report

Tell the user:

Issue ID and title
Priority and labels
Brief summary of what needs to be done
Whether this is a parent issue (needs planning via /linear-plan) or a sub-issue (ready for /linear-implement)
Any dependencies or related issues

Rules

Do NOT pick up work if there are already 2+ issues assigned to you in "In Progress" state
Do NOT pick up "Backlog" issues — only "Todo"
Do NOT pick up "Canceled" issues
If no Todo issues exist, report "No available work" and suggest the user check Backlog for items to promote

このリポジトリの他の Skills

同じリポジトリ

linear-implement

Desgue/landscaper

Implement a Linear sub-issue end-to-end. Creates a branch, writes the code, runs tests, commits, and moves the issue to In Review. Use when an agent has a sub-issue to implement, or the user says "implement this issue", "/linear-implement".

2026-04-080

linear-complete

Desgue/landscaper

Finalize a parent Linear issue after all sub-issues are Done. Verifies acceptance criteria, runs final checks, and closes the parent. Use when all sub-issues of a parent are done, or the user says "complete this", "/linear-complete".

2026-04-080

linear-plan

Desgue/landscaper

Explore the codebase and write a detailed implementation plan into a Linear parent issue's description. Creates sub-issues for each atomic task. Use when an agent has picked up a parent issue and needs to plan the work, or the user says "plan this issue", "/linear-plan".

2026-04-080

linear-review

Desgue/landscaper

Review a Linear issue that is In Review. Checks code quality, tests, types, and regressions. Approves (moves to Done) or requests changes (moves to Revise). Use when the user says "review this", "/linear-review", or an issue needs review.

2026-04-080

linear-revise

Desgue/landscaper

Handle a Linear issue in Revise state. Reads reviewer feedback, fixes the code, re-verifies, and moves back to In Review. Use when an issue has been sent back for changes, or the user says "/linear-revise".

2026-04-080

linear-setup

Desgue/landscaper

One-time setup of the Linear Landscaper project. Creates custom workflow states, labels, and milestones. Use when setting up Linear for the first time or the user says "/linear-setup".

2026-04-080

ソース

Desgue

Desgue/landscaper

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

造園・敷地整備従事者建物・敷地清撃・維持管理職37-3011L4

name	linear-pickup
description	Scan the Linear Landscaper project for the next available issue to work on. Checks Todo items by priority, verifies dependencies are met, claims the issue, and reports what to do next. Use when an agent needs to find work or the user says "pick up work", "what's next", or "/linear-pickup".
allowed-tools	["Read","Grep","Glob","Bash(git:*)"]
argument-hint	[optional: label filter e.g. Bug, Spike]

Pick Up Work from Linear

Find the next issue to work on in the Landscaper project.

Context

Team: Engineering (ENG)
Project: Landscaper
Workflow doc: docs/LINEAR-WORKFLOW.md
Description templates: docs/plans/PLAN_TEMPLATE.md

Process

1. Scan Todo issues

Use mcp__linear-server__list_issues to find issues:

Filter: state: "Todo", project: "Landscaper"
If $ARGUMENTS is provided, also filter by label name matching $ARGUMENTS
Sort by priority (Urgent=1 first, then High=2, Medium=3, Low=4)

2. Check dependencies

For each candidate issue (highest priority first):

Use mcp__linear-server__get_issue to read full details
Check the blockedBy field — if any blocking issue is NOT in "Done" state, skip this issue
Check if the issue has a blocker label — if yes, skip

3. Claim the issue

Once a valid issue is found:

Use mcp__linear-server__save_issue to set state: "In Progress"
Use mcp__linear-server__save_comment to post: "Taking this."
If the issue has no estimate, add one (1=small, 3=medium, 5=large based on description complexity)

4. Report

Tell the user:

Issue ID and title
Priority and labels
Brief summary of what needs to be done
Whether this is a parent issue (needs planning via /linear-plan) or a sub-issue (ready for /linear-implement)
Any dependencies or related issues

Rules

Do NOT pick up work if there are already 2+ issues assigned to you in "In Progress" state
Do NOT pick up "Backlog" issues — only "Todo"
Do NOT pick up "Canceled" issues
If no Todo issues exist, report "No available work" and suggest the user check Backlog for items to promote