flowstate-app-bizdev Package Skill

Package: @epicdm/flowstate-app-bizdev Repository: epic-flowstate-apps Path: packages/flowstate-app-bizdev Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

BizDev CRUD Forms

Status: Active Purpose: Keep collection hooks, forms, and Zod validation aligned. Scope: packages/flowstate-app-bizdev/src/hooks, src/schemas, and entity components. Trigger: Work changes create, edit, delete, list, or detail behavior for BizDev entities. Input: Target entity and desired behavior. Output: Hook, schema, form, and UI updates that match collection behavior.

Workflow

1. Start with the entity hook: useOpportunityCRUD.ts, usePartnershipCRUD.ts, useOutreachTargetCRUD.ts, useActivityCRUD.ts, useClientCRUD.ts, or useContactCRUD.ts.
2. Check the matching schema in src/schemas. User-entered fields should be validated with Zod before mutation.
3. Update the form component under src/components/<entity> and preserve route-param create/edit behavior.
4. Keep collection names stable: opportunities, partnerships, outreachtargets, activities, clients, and contacts.
5. For activities, check useActivityCRUD.ts comments and ActivityForm.tsx; activities are primarily create/timeline records.

Example

For a new opportunity field, add it to opportunityFormSchema, update OpportunityForm.tsx, then check OpportunityList.tsx, OpportunityDetail.tsx, and OpportunityKanban.tsx for display and grouping implications.

Verification

• yarn workspace @epicdm/flowstate-app-bizdev typecheck
• Add a focused test for schema or form behavior if validation branches change.

Created: 2026-06-30

Package Skill Inventory

FlowState BizDev Skill Inventory

Reviewed: 2026-06-30

Skills

Review Gate

FlowState BizDev Skills Review

Reviewed: 2026-06-30 Status: Pass

Checks

• Skills are grounded in hooks, schemas, plugin routes, and component workflows.
• Skills call out Zod schema maintenance for user input.
• Skills avoid generated .flowstate/dojo files.

Residual Risk

Some mutation hooks use as any around mutation-like objects. When changing those hooks, add focused type coverage or component tests rather than relying on the package test script, which currently reports no tests.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-app-bizdev/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.