OpenParable
Skip to content

Productivity skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

add-lesson

Add a new lesson learned to shared rules and sync to context files.

498 repo stars78 repo forks
Productivity

ag-vorbereitung

Vorbereitung auf das Aufrufen in der Arbeitsgemeinschaft (AG) oder im Seminar. Lade diesen Skill bei Anfragen wie „AG-Vorbereitung", „Seminar vorbereiten", „was fragt der Dozent", „Cold Call" oder „ich werde morgen drangenommen".

498 repo stars78 repo forks
Productivity

agent-ops-housekeeping

Comprehensive project hygiene: archive issues, validate schema, clean clutter, align docs, check git, update ignores.

498 repo stars78 repo forks
Productivity

agile-v-lifecycle

Multi-cycle iteration management, document versioning, change requests, re-entry points, archival, and impact analysis. Load when starting a new cycle (C2+), processing change requests, or managing cross-cycle traceability.

498 repo stars78 repo forks
Productivity

AgilePm

Enterprise agile product management workflows for PAI. USE WHEN user needs PRD creation, epic decomposition, user story generation, sprint planning, or structured agile project management. Provides BMAD-quality rigor with PAI simplicity.

498 repo stars78 repo forks
Productivity

ai-standup

Use when preparing daily standup notes or summarizing recent PR and commit activity for team updates.

498 repo stars78 repo forks
Productivity

aico-backend-task-breakdown

Break down PM story into independent backend task files following LAYERED ARCHITECTURE order: Types → Database → Repository → Service → API → Tests. UNIQUE VALUE: Creates independent task files (story-{name}-{n}-{task}.md) for each task. Tasks are ordered by backend architecture layers. Use this skill when: - Running /backend.tasks command - User asks to "break down story", "create backend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task files - Need tasks ordered by backend architecture layers (not random order) - Starting backend work and want organized task list Task order is CRITICAL: Setup → Static UI → Dynamic → Interactions → Tests Output: Create multiple files in docs/reference/backend/tasks/ with story- prefix

498 repo stars78 repo forks
Productivity

aico-frontend-task-breakdown

Break down PM story into independent frontend task files following UI DEVELOPMENT order: Setup → Static UI → Dynamic Logic → Interactions → Testing. UNIQUE VALUE: Creates independent task files (story-{name}-{n}-{task}.md) for each task. Tasks are ordered by UI development layers. Use this skill when: - Running /frontend.tasks command - User asks to "break down story", "create frontend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task files - Need tasks ordered by UI development layers (not random order) - Starting frontend work and want organized task list Task order is CRITICAL: Setup → Static UI → Dynamic → Interactions → Tests Output: Create multiple files in docs/reference/frontend/tasks/ with story- prefix

498 repo stars78 repo forks
Productivity

aico-pm-user-story-writing

Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user story", "create story", "add story" - User mentions "user story", "backlog item", "story" - Running /pm.plan and need to break PRD into implementable stories - Creating backlog items for development team - Need to formalize a requirement into standard story format - Converting feature request into actionable story with acceptance criteria Output: ALWAYS write story files to docs/reference/pm/stories/{story-name}.md

498 repo stars78 repo forks
Productivity