Discover facts
Find documents, statuses, hooks, and callers before you plan.
Outcome
You know what the code does, or you know the next path to open. You do not hold a workspace plan yet.
Prerequisites
- A Logic Bee API workspace with
.agents/skills/logic-discovery/SKILL.md - A topic in one sentence, or a hook path if you have one
Call the skill
/logic-discovery
If that slash name does not start the skill, put @.agents/skills/logic-discovery/SKILL.md on line 1.
Name type in the first prompt when you know it:
discovery: bug | feature | idea | requirement | question
After every discovery answer, the skill asks whether to dig deeper. Say stop or name the next path.
question and idea stop the pipeline. Do not start /logic-plan for those types.
Minimal example
This example uses the same void hook as Run the pipeline. The operation is compound. No change is requested.
/logic-discovery
type: question
How does voiding a posted customer invoice work? Start from
`finance-invoices/void-invoice`. Name the documents, statuses, and
downstream hooks. Do not propose a change.
Expected result: Named documents, statuses, and downstream hooks. No proposed change.
Type bug
Trace expected vs actual. Stop at the divergence. No cause. No fix.
/logic-discovery
type: bug
After voiding a posted invoice, the sales order still shows the old
`orderLines[].quantityInvoiced`. Trace expected vs actual from
`finance-invoices/void-invoice`. Stop at the divergence. No cause, no fix.
Type feature
New behaviour on an existing report. finance-reports/account-credit-exposure-report (pattern: 'report'). Tiers: Over Limit, 75–100%, 50–75%, Under 50%, No Outstanding Balance, No Limit Set.
/logic-discovery
type: feature
Add a 90–100% utilization tier to
`finance-reports/account-credit-exposure-report`.
Sweep documents, fields, and callers. Narrow with me before planning.
Type requirement
Change an existing guard. procurement/delete-purchase-order (pattern: 'delete-document'): only draft purchase orders may be deleted.
/logic-discovery
type: requirement
"Cancelled purchase orders should be deletable the same way as drafts."
Inventory `procurement/delete-purchase-order`, the PO status enum, and
anything that assumes deleted POs were never confirmed.
Type idea
Feasibility only. Do not design phases. finance-fiscal-periods/ensure-fiscal-years-and-periods (pattern: 'ensure', idempotent: true). Rolling year window. Key data.year.
/logic-discovery
type: idea
When finance settings change fiscal month, should
`finance-fiscal-periods/ensure-fiscal-years-and-periods` rebuild the
rolling year window, or is that a new hook? Look up; do not design phases.
Omit type
Omit type on purpose when the problem is not named yet. The skill must ask. The user does not name the hook. Captions below are for you. They are not part of the prompt.
Likely bug — finance-payments/void-check
Bill stays paid. Check vs credit mix-up.
/logic-discovery
voided a check (or a credit? someone said memo) and the bill still looks paid.
inventory? payables? not sure what to look at.
Likely question — finance-fiscal-periods/close-fiscal-year
/logic-discovery
year end is stuck. or the period. finance said retained earnings.
what's even supposed to happen?
Likely bug — sales-blanket-orders/restore-blanket-order-quantity
/logic-discovery
cancelled a sales order that was on a contract and the leftover qty
didn't come back. is that blankets? quotes? something else.
Likely question — inventory-management/sync-next-cycle-count-date
/logic-discovery
we turned a cycle count schedule off and the next date is still sitting there.
bug or by design? i don't know the names.
Likely idea — drop-ship receive vs invoice
procurement-ai/receive-dropshipping-purchase-order
/logic-discovery
dropship — vendor ships to the customer and then people forget to invoice.
should receiving just invoice too? or is that a different button.
don't plan anything yet.
Likely bug — shipping-ai/generate-invoice-from-bill-of-lading
/logic-discovery
invoiced from the packing slip / bol / whatever and now invoiced qty
looks like it doubled. or the so is wrong. start somewhere.
Likely question — manufacturing-ai/move-manufacturing-quantity
/logic-discovery
moved a job to another warehouse (or split it? both?) and the sales
order / bol / work orders look off. what does that flow actually touch.
Likely question — finance-journal-templates/check-journal-entry-templates-schedule
/logic-discovery
the recurring journals. some posted, some didn't, one is paused?
i don't know if that's a schedule or a template or a cron.
Likely bug — payment-log/process-bank-import
/logic-discovery
uploaded the bank csv. some lines came in, some didn't, finance says
duplicates. or missing. i can't tell expected vs actual yet.
Likely requirement — manufacturing/create-manufacturing-order
Create vs validate vs cost.
/logic-discovery
new MOs should just work from the item / bom / routing. right now
create fails or costs are empty or validation yells. not sure which
and whether that's a requirement or a bug.
If the topic is unknown
/logic-discovery
type: question
Broad sweep first. I will tell you what to narrow.
Topic: <one sentence>
A named handoff from /logic-plan can send Problem: with want: / got:. Example:
/logic-discovery
Problem:
want: bank import rejects a duplicate hash before a payment-log row is created
got: a second row is created with the same hash
Next
- Plan the workspace after
bug,feature, orrequirement - Plan one hook when the work is already one hook
- Rule index in the workspace:
.agents/rules/catalog.md