apenlor

Decompose a confirmed epic into user story candidates using a facilitated decomposition strategy. Triggers: "decompose epic", "break down epic", "stories from epic", "epic to stories", "slice this epic", or any request to derive stories from an existing epic.

Jira skill for creating, querying, and updating issues across any Jira project. Triggers: "create an epic", "create a bug", "show me bugs", "epics in progress", "issues completed", "bugs due in N days", or any Jira request. Also triggers when other skills (e.g. write-us, write-epic-build) reach a Jira confirmation step.

Tidy an initiative's output folder: inventory files, promote valuable artifacts, consolidate drafts, extract product knowledge, update shared data, and clean up stale files. Triggers: "tidy initiative", "clean up initiative", "organize output", "tidy output", or any request to review and clean an initiative's output folder.

Write a Build Epic for implementing a feature or technical solution. Triggers: "write an epic", "create an implementation epic", "new feature epic", "build this", "implementation plan", or any request to define delivery as an Epic.

Write a Technical Discovery Epic for reducing technical uncertainty. Triggers: "write a technical discovery", "create a discovery epic", "technical discovery", or any request to define a technical investigation as an Epic.

Write a User Story following INVEST principles and vertical slicing. Triggers: "write a US", "write a user story", "write a story", "new user story", or any request to draft a feature or change as a story.

Log the outcomes of a completed 1:1 meeting. Records topics, commitments, and signals in a structured per-person history file. Triggers: "log my 1:1 with", "record 1:1", "save 1:1 notes", "log 1:1", or any request to capture 1:1 outcomes.

Go from a rough idea to a structured initiative with clear scope, approach, and epics. Triggers: "plan an initiative", "help me structure this initiative", "I want to kick off", "we need to tackle", or any request to shape significant work before execution.

Explore ideas and create designs before implementation

Use when about to claim work is complete or before committing - enforces verification and proposes a commit

Fetch current library and framework documentation from Context7 instead of relying on training data

Use when you have a written implementation plan to execute - direct execution by default, subagents for complex tasks

Use when encountering any bug, test failure, or unexpected behavior — find root cause before proposing any fix

Use when implementing any feature or bugfix, before writing implementation code

Use when starting substantive work to choose the right workflow skill without adding unnecessary ceremony to trivial interactions

Use when you have a spec or requirements for a multi-step task, before touching code