skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

organize

Groups tracker issues referencing specs or ADRs into project-based structures.

30|2|Updated Feb 13, 2026
Search Tags:#governance#organize#issues#projects#sprints#boards#tracker
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill organize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: organize
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/organize
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill organize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retroactively group existing tracker issues into tracker-native projects to improve organization, reporting, and governance.

Core Features & Use Cases

  • Identify issues referencing a SPEC or ADR and group them into cohesive projects, epics, and boards.
  • Create or enrich project-level context (descriptions, README, views, iteration fields, and milestones) without modifying individual issues in Tier A.
  • Reorganize and enrich workflows across trackers, with configuration via .claude-plugin-design.json and graceful degradation if features are unavailable.

Quick Start

Provide a SPEC-XXXX or capability name to organize, then review the proposed project structure in dry-run mode.

Frequently Asked Questions about organize

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

FAQPage Schema
How do I group existing tracker issues into projects for sprint governance?▼

Grouping existing issues into tracker-native projects enables scalable sprint governance without modifying individual issue content. You provide a SPEC-XXXX or capability name to organize related work into cohesive projects, epics, and boards.

Can I organize issues into epics and boards without modifying the original issue content?▼

Yes, you can organize issues into epics and boards without modifying issue content by using dry-run mode. This Tier A approach creates or enriches project-level context like descriptions, views, and milestones while leaving individual issues untouched.

How do I reorganize issues referencing a SPEC or ADR into cohesive tracker projects?▼

Reorganizing issues referencing a SPEC or ADR involves identifying those issues and grouping them into cohesive tracker-native projects, epics, and boards. Configuration is managed via the .claude-plugin-design.json file to define the project structure.

Does tracker project organization work across common issue trackers when features are unavailable?▼

Tracker project organization works across common trackers and degrades gracefully when tracker features are unavailable. This ensures reorganization and enrichment workflows continue functioning even without full native project support.

What are the limitations of retroactively grouping issues into tracker-native projects?▼

Limitations of retroactively grouping issues include reliance on tracker-specific features for creating iteration fields or milestones. If native tracker features are unavailable, the organization degrades gracefully, limiting the ability to enrich project-level context.

Related Skills

Explore More Software Engineering Skills→
Clay-HHKClay-HHK
2

Plugin Structure

Create and organize Claude Code plugin structures with plugin.json manifests.

Community
Advanced
nnexainnexai
1

gsd-add-phase

Add project phases to roadmaps with sequential identifiers and state files.

Community
Intermediate
eric-sabeeric-sabe
1

issue-tracker-github

Manage GitHub Issues and ProjectV2 boards via gh CLI and GraphQL.

Community
Advanced
kinncjkinncj
23

gh-projects

Automates GitHub Project V2 board management by adding issues and updating fields.

Community
Intermediate