Sync sprint backlog from architecture blueprint to project management tools (Linear, Jira, GitHub Issues, Asana, ClickUp). Creates issues/tasks with user stories, acceptance criteria, priorities, and sprint assignments.
Sync sprint backlog from architecture blueprints to project management tools like Linear, Jira, or GitHub Issues.
npx claudepluginhub navraj007in/architecture-cowork-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Push your architecture blueprint's sprint backlog to project management tools for immediate sprint planning and development.
Perfect for: Sprint planning, team collaboration, task tracking, agile workflows
Use this skill when you need to:
Input: Architecture blueprint (Section 15: Sprint Backlog) Output: Issues/tasks created in Linear, Jira, GitHub, Asana, or ClickUp
Why Linear:
What's Created:
API Requirements:
Why GitHub Issues:
What's Created:
API Requirements:
owner/repo)Why Jira:
What's Created:
API Requirements:
yourcompany.atlassian.net)PROJ)Why Asana:
What's Created:
API Requirements:
Why ClickUp:
What's Created:
API Requirements:
Extract from Section 15: Sprint Backlog:
## Sprint 0: Project Setup & Infrastructure (Week 1)
**Goal**: Production-ready foundation
### User Stories
#### US-0.1: Developer can deploy to production
**Priority**: High
**Story Points**: 5
**Description**: Set up CI/CD pipeline so any developer can deploy code to production with a single command.
**Acceptance Criteria**:
- [ ] GitHub Actions workflow configured
- [ ] Deploys on push to `main` branch
- [ ] Automated tests run before deploy
- [ ] Deploy to Vercel (frontend) and Railway (backend)
- [ ] Environment variables configured
- [ ] Can rollback to previous version
**Technical Notes**:
- Use GitHub Actions for CI/CD
- Vercel for frontend (auto-deploy)
- Railway for backend workers
- Store secrets in GitHub Secrets
---
#### US-0.2: Database is provisioned and migrations run
**Priority**: High
**Story Points**: 3
**Description**: Set up PostgreSQL database with Prisma ORM and run initial migration.
**Acceptance Criteria**:
- [ ] Supabase project created
- [ ] Database connection string in .env
- [ ] Prisma schema matches blueprint
- [ ] Initial migration applied
- [ ] Seed data loaded
- [ ] Can query database from app
**Technical Notes**:
- Use Supabase free tier
- Prisma for ORM
- RLS policies for multi-tenancy
[... more user stories ...]
Linear Format:
{
"title": "US-0.1: Developer can deploy to production",
"description": "Set up CI/CD pipeline so any developer can deploy code to production with a single command.\n\n**Acceptance Criteria**:\n- [ ] GitHub Actions workflow configured\n- [ ] Deploys on push to `main` branch\n- [ ] Automated tests run before deploy\n- [ ] Deploy to Vercel (frontend) and Railway (backend)\n- [ ] Environment variables configured\n- [ ] Can rollback to previous version\n\n**Technical Notes**:\n- Use GitHub Actions for CI/CD\n- Vercel for frontend (auto-deploy)\n- Railway for backend workers\n- Store secrets in GitHub Secrets",
"priority": 1,
"estimate": 5,
"labelIds": ["<high-priority-label-id>", "<infrastructure-label-id>"],
"projectId": "<sprint-0-project-id>",
"teamId": "<team-id>"
}
GitHub Issues Format:
{
"title": "US-0.1: Developer can deploy to production",
"body": "**Priority**: High\n**Story Points**: 5\n\n**Description**: Set up CI/CD pipeline so any developer can deploy code to production with a single command.\n\n**Acceptance Criteria**:\n- [ ] GitHub Actions workflow configured\n- [ ] Deploys on push to `main` branch\n- [ ] Automated tests run before deploy\n- [ ] Deploy to Vercel (frontend) and Railway (backend)\n- [ ] Environment variables configured\n- [ ] Can rollback to previous version\n\n**Technical Notes**:\n- Use GitHub Actions for CI/CD\n- Vercel for frontend (auto-deploy)\n- Railway for backend workers\n- Store secrets in GitHub Secrets",
"labels": ["Sprint 0", "Priority: High", "Type: Infrastructure"],
"milestone": "Sprint 0",
"assignees": []
}
Jira Format:
{
"fields": {
"project": { "key": "PROJ" },
"summary": "US-0.1: Developer can deploy to production",
"description": "Set up CI/CD pipeline so any developer can deploy code to production with a single command.\n\nh3. Acceptance Criteria\n* GitHub Actions workflow configured\n* Deploys on push to main branch\n* Automated tests run before deploy\n* Deploy to Vercel (frontend) and Railway (backend)\n* Environment variables configured\n* Can rollback to previous version\n\nh3. Technical Notes\n* Use GitHub Actions for CI/CD\n* Vercel for frontend (auto-deploy)\n* Railway for backend workers\n* Store secrets in GitHub Secrets",
"issuetype": { "name": "Story" },
"priority": { "name": "High" },
"customfield_10016": 5,
"labels": ["sprint-0", "infrastructure"],
"sprint": "<sprint-id>"
}
}
Before creating issues, set up organizational structure:
Linear:
// Create projects for each sprint
const sprint0 = await linear.createProject({
name: "Sprint 0: Project Setup & Infrastructure",
description: "Production-ready foundation",
startDate: "2026-02-07",
targetDate: "2026-02-14",
teamId: teamId,
});
const sprint1 = await linear.createProject({
name: "Sprint 1: Authentication & User Management",
description: "User signup, login, workspace creation",
startDate: "2026-02-14",
targetDate: "2026-02-28",
teamId: teamId,
});
GitHub:
# Create milestones
gh api repos/{owner}/{repo}/milestones \
-f title="Sprint 0: Project Setup & Infrastructure" \
-f description="Production-ready foundation" \
-f due_on="2026-02-14T00:00:00Z"
gh api repos/{owner}/{repo}/milestones \
-f title="Sprint 1: Authentication & User Management" \
-f description="User signup, login, workspace creation" \
-f due_on="2026-02-28T00:00:00Z"
Jira:
# Create sprints
curl -X POST https://yourcompany.atlassian.net/rest/agile/1.0/sprint \
-H "Authorization: Basic $(echo -n email:token | base64)" \
-H "Content-Type: application/json" \
-d '{
"name": "Sprint 0",
"startDate": "2026-02-07T08:00:00.000Z",
"endDate": "2026-02-14T17:00:00.000Z",
"originBoardId": <board-id>
}'
For each user story:
Linear:
const issue = await linear.createIssue({
teamId: teamId,
projectId: sprint0.id,
title: "US-0.1: Developer can deploy to production",
description: descriptionMarkdown,
priority: 1, // 0=No priority, 1=Urgent, 2=High, 3=Medium, 4=Low
estimate: 5, // Story points
labelIds: [highPriorityLabelId, infrastructureLabelId],
});
GitHub:
gh issue create \
--repo owner/repo \
--title "US-0.1: Developer can deploy to production" \
--body "$DESCRIPTION" \
--label "Sprint 0,Priority: High,Type: Infrastructure" \
--milestone "Sprint 0"
Jira:
curl -X POST https://yourcompany.atlassian.net/rest/api/3/issue \
-H "Authorization: Basic $(echo -n email:token | base64)" \
-H "Content-Type: application/json" \
-d @issue-payload.json
If blueprint specifies dependencies:
Linear (blocking relationships):
await linear.createIssueRelation({
issueId: issue1.id,
relatedIssueId: issue2.id,
type: "blocks", // issue1 blocks issue2
});
GitHub (task lists in description):
## Dependencies
- Blocked by #12 (Database setup)
- Blocks #15 (User authentication)
Jira (issue links):
{
"type": { "name": "Blocks" },
"inwardIssue": { "key": "PROJ-1" },
"outwardIssue": { "key": "PROJ-2" }
}
Create and apply labels:
Priority Labels:
Type Labels:
Sprint Labels:
Component Labels (from feature areas):
When invoked, generate:
🔄 Syncing sprint backlog to Linear...
✅ Detected 8 sprints in blueprint (56 user stories total)
✅ Connected to Linear workspace: Acme Corp
✅ Team: Engineering (team_abc123)
📋 Creating organizational structure...
✅ Created project: Sprint 0 (Feb 7 - Feb 14)
✅ Created project: Sprint 1 (Feb 14 - Feb 28)
✅ Created project: Sprint 2 (Feb 28 - Mar 14)
[... more sprints ...]
🏷️ Creating labels...
✅ Priority: High
✅ Priority: Medium
✅ Priority: Low
✅ Type: Feature
✅ Type: Bug
✅ Type: Tech Debt
✅ Component: Authentication
✅ Component: Database
[... more labels ...]
📝 Creating issues...
✅ US-0.1: Developer can deploy to production (5 pts, High)
✅ US-0.2: Database is provisioned and migrations run (3 pts, High)
✅ US-0.3: Environment variables configured (2 pts, Medium)
[... 53 more issues ...]
🔗 Linking dependencies...
✅ Linked 12 blocking relationships
📊 Summary:
- Sprints: 8
- Total issues: 56
- Story points: 134
- High priority: 18
- Medium priority: 28
- Low priority: 10
🎯 View in Linear:
https://linear.app/acme-corp/project/sprint-0
Next steps:
1. Review issues in Linear
2. Assign team members to issues
3. Start Sprint 0 and begin development
4. Update issue status as work progresses
Create all issues once, no ongoing sync.
Use when: Initial project setup, blueprint is final.
/architect:sync-backlog --platform=linear
Keep blueprint and Linear in sync.
Use when: Blueprint evolves, need to track changes.
Features:
/architect:sync-backlog --platform=linear --mode=two-way
Generate CSV/JSON for manual import.
Use when: No API access, need manual review before import.
/architect:sync-backlog --platform=csv
# Output: backlog-export.csv
Optional parameters:
Examples:
# Sync to Linear with 1-week sprints
/architect:sync-backlog --platform=linear --sprint-duration=1-week
# Sync to GitHub with auto-assignment
/architect:sync-backlog --platform=github --repo=owner/repo --assign=@me
# Dry run (preview only)
/architect:sync-backlog --platform=jira --dry-run
# Export to CSV
/architect:sync-backlog --platform=csv --output=backlog.csv
Keyboard Shortcuts Support: Add keyboard shortcut hints in issue descriptions:
**Quick Actions**:
- `c` - Complete this issue
- `a` - Assign to me
- `l` - Add label
- `p` - Change priority
Cycles Integration: Map sprints to Linear cycles automatically:
/architect:sync-backlog --platform=linear --use-cycles
# Creates or updates cycles for each sprint
GitHub Projects Integration: Create a GitHub Project board automatically:
/architect:sync-backlog --platform=github --create-project
# Creates: "Architecture Implementation" project
# Columns: Backlog, Sprint 0, Sprint 1, ..., In Progress, Done
Issue Templates:
Generate .github/ISSUE_TEMPLATE/user-story.md:
---
name: User Story
about: User story from architecture blueprint
labels: user-story
---
**Priority**:
**Story Points**:
**Description**:
**Acceptance Criteria**:
- [ ]
- [ ]
**Technical Notes**:
Epics Mapping: Create epics for major feature areas:
Epic: Authentication System
├─ US-1.1: User signup
├─ US-1.2: Email verification
└─ US-1.3: Password reset
Epic: Ticket Management
├─ US-2.1: Create ticket
├─ US-2.2: Update ticket
└─ US-2.3: Close ticket
Confluence Integration: Generate Confluence page with:
/architect:sync-backlog --platform=jira --create-confluence-doc
/architect:blueprint first."For manual import or tools without API:
Sprint,ID,Title,Description,Priority,Story Points,Acceptance Criteria,Technical Notes,Labels
Sprint 0,US-0.1,Developer can deploy to production,"Set up CI/CD pipeline...",High,5,"- [ ] GitHub Actions workflow configured
- [ ] Deploys on push to main branch","Use GitHub Actions for CI/CD
Vercel for frontend","infrastructure,devops"
Sprint 0,US-0.2,Database is provisioned and migrations run,"Set up PostgreSQL...",High,3,"- [ ] Supabase project created
- [ ] Database connection string in .env","Use Supabase free tier
Prisma for ORM","database,setup"
[...]
Import instructions included in output:
📄 CSV exported to: backlog-export.csv
To import:
- Linear: Import via CSV at linear.app/settings/import
- Jira: Tools → Import → CSV
- GitHub: Use gh-issues-import script
- Asana: Import via CSV at app.asana.com/import
A successful backlog sync should:
/architect:sync-backlog --platform=linear
# Interactive prompts:
# - Linear API key: [paste from linear.app/settings/api]
# - Team: Engineering (auto-detected)
# - Start date: 2026-02-07 (today)
# - Sprint duration: 2 weeks
# Output: 56 issues created across 8 sprints
/architect:sync-backlog --platform=github --repo=acme/backend
# Requires: gh CLI authenticated
# Creates: Milestones + Issues + Labels
# Output: Link to project board
/architect:sync-backlog --platform=jira
# Interactive prompts:
# - Jira URL: acme.atlassian.net
# - Email: you@acme.com
# - API token: [from id.atlassian.com]
# - Project key: PROJ
# Output: 56 stories created in PROJ project
/architect:sync-backlog --platform=csv --output=backlog.csv
# Output: backlog.csv (ready for manual import)
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.