组织
Eliyce
AI delivery you can review. Dutch software company building software and AI agents. Makers of Paqad, the open-source AI delivery framework.
- Skills
- 20
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 8
Eliyce 的 Skills 20
start
Chat and Claude Code: One place to start for product work, routing you to the capability that fits. Use it when you want help with product work and a single place to begin ("help me with this ticket", "I have an idea", "what can you do here?", "where do I start?"). It reads what you are after, names the capability that handles it, and hands you straight to it behind the scenes, so you only have to remember one entry. It is a thin router: it does no drafting, keeps no record, and writes nothing to the tracker itself; the capability it hands you to does that work.
ask
Chat and Claude Code: Answers business questions about the product from the project's own documentation and code, in plain words with sources. Use it when someone asks what the product is, what it does or what areas it has ("what is this product?", "what does this project do?", "what areas does it have?"), when a repository is attached or connected and the user asks what it is or what it does, or when they ask how something works today ("can customers pause a subscription today?", "who uses the export screen?", "which orders go to the finance system?"). It works on any repository at the best evidence level it can reach, reads only what the question needs, leads with the answer, adds one short Sources line and one short source line for the level, shows the project's own term on first use, and says honestly where the documents cannot confirm something. It never writes to the tracker, and it can offer to carry a question into the idea journey when the answer reveals a gap.
front-door
Chat and Claude Code: One place to start for product work, routing you to the capability that fits. Use it when you want help with product work and a single place to begin ("help me with this ticket", "I have an idea", "what can you do here?", "where do I start?"). It reads what you are after, names the capability that handles it, and hands you straight to it behind the scenes, so you only have to remember one entry. It is a thin router: it does no drafting, keeps no record, and writes nothing to the tracker itself; the capability it hands you to does that work.
ask-project
Chat and Claude Code: Answers business questions about the product from the project's own documentation and code, in plain words with sources. Use it when someone asks what the product is, what it does or what areas it has ("what is this product?", "what does this project do?", "what areas does it have?"), when a repository is attached or connected and the user asks what it is or what it does, or when they ask how something works today ("can customers pause a subscription today?", "who uses the export screen?", "which orders go to the finance system?"). It works on any repository at the best evidence level it can reach, reads only what the question needs, leads with the answer, adds one short Sources line and one short source line for the level, shows the project's own term on first use, and says honestly where the documents cannot confirm something. It never writes to the tracker, and it can offer to carry a question into the idea journey when the answer reveals a gap.
write-tickets
Chat and Claude Code: Step 5 of the discover journey: drafts epics and user-story tickets with Given/When/Then acceptance criteria into the ticket set and a preview. Also redrafts the ticket set and its preview when the person changes the draft during the journey, for example moving a group of tickets to a different epic or a new one, and asks for approval again. Use when the journey directs it to step 5 or back to it for a redraft, not directly.
shape-idea
Chat and Claude Code: Step 3 of the discover journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly.
post-tickets
Chat and Claude Code: Step 6 of the discover journey: posts the approved tickets to the tracker or exports a CSV, links them and reads them back to confirm. At hand-off it also writes the short summary of the decision and the next action when the outcome is not a build (experiment, already exists, process change, defer or stop). Use when the journey directs it to step 6 or to the hand-off, not directly.
ground-in-project
Chat and Claude Code: Step 2 of the discover journey: records what exists today for the idea from the project's documents and code, with sources. Use when the journey directs it to step 2, not directly.
get-connected
Chat and Claude Code: Step 0 of the discover journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.
discover
Chat and Claude Code: Shape an idea or a problem into clear epics and tickets, or into another sensible outcome, as a product consultant. Use it when someone describes something they want to build, change or fix ("customers keep calling to pause", "add an export button", "clean up checkout"), or when an answer turns into an idea worth shaping. It moves through six steps in order, grounded in the project's own documents and, when a tracker is connected, its existing epics and tickets: get connected, your idea, what exists today, shape it, decide, draft and check, then post to the tracker on an explicit go-ahead. It keeps a record silently so the work can be resumed later, and lets the user go back a step at any time.
decide-together
Chat and Claude Code: Step 4 of the discover journey: settles each open choice with the user, weighing the options, and records every decision and assumption. Use when the journey directs it to step 4, not directly.
check-tickets
Chat and Claude Code: Step 5 of the discover journey: reviews the drafted tickets for plain prose, story structure and duplicates, and flags fixes before anything is posted. Use when the journey directs it to step 5, not directly.
write-tickets
Chat and Claude Code: Step 5 of the product-discovery journey: drafts epics and user-story tickets with Given/When/Then acceptance criteria into the ticket set and a preview. Also redrafts the ticket set and its preview when the person changes the draft during the journey, for example moving a group of tickets to a different epic or a new one, and asks for approval again. Use when the journey directs it to step 5 or back to it for a redraft, not directly.
shape-idea
Chat and Claude Code: Step 3 of the product-discovery journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly.
product-discovery
Chat and Claude Code: Shape an idea or a problem into clear epics and tickets, or into another sensible outcome, as a product consultant. Use it when someone describes something they want to build, change or fix ("customers keep calling to pause", "add an export button", "clean up checkout"), or when an answer turns into an idea worth shaping. It moves through six steps in order, grounded in the project's own documents and, when a tracker is connected, its existing epics and tickets: get connected, your idea, what exists today, shape it, decide, draft and check, then post to the tracker on an explicit go-ahead. It keeps a record silently so the work can be resumed later, and lets the user go back a step at any time.
post-tickets
Chat and Claude Code: Step 6 of the product-discovery journey: posts the approved tickets to the tracker or exports a CSV, links them and reads them back to confirm. At hand-off it also writes the short summary of the decision and the next action when the outcome is not a build (experiment, already exists, process change, defer or stop). Use when the journey directs it to step 6 or to the hand-off, not directly.
ground-in-project
Chat and Claude Code: Step 2 of the product-discovery journey: records what exists today for the idea from the project's documents and code, with sources. Use when the journey directs it to step 2, not directly.
get-connected
Chat and Claude Code: Step 0 of the product-discovery journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.