fulcra-fde

Runs structured engagements that turn business ideas into working software built on Fulcra primitives.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-fde-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-fde
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-fde
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-fde-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fde-engine, fulcra-api, and includes references (resource) components.

What problem does it solve? Turning a business plan, pitch deck, or product idea into working software requires structured discovery, architecture decisions, and verified prototypes — this Skill provides a repeatable engagement lifecycle that ends in a real product backed by the Fulcra platform. ## Core Features & Use Cases - Structured engagement lifecycle: Drives intake, interview, architecture, plan, prototype, build, and retro phases with durable, resumable state stored in the user's own Fulcra file store via the fde-engine CLI. - Real-data prototyping: Requires prototypes to bind to the user's actual Fulcra data types (discovered via fulcra catalog) and create custom data types for novel streams — mock data counts as a failed verification. - Capability mapping and gap register: Maps product needs to Fulcra primitives (records, files, tags, data-updates) and documents design-arounds for platform gaps like missing webhooks or cross-user datashare. - Use Case: A founder brings a pitch deck for a health-tracking product; the Skill interviews them, maps needs to Fulcra data types, builds a verification prototype on their real data, then executes the production build. ## Quick Start Ask the agent to act as a Fulcra forward-deployed engineer and start a new engagement from your business plan or product idea document.

Frequently Asked Questions about fulcra-fde

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a product on Fulcra from a business plan?

Start an engagement with `fde-engine init <slug>`, then follow the lifecycle: intake the source materials, run a structured interview, map needs to Fulcra primitives, prototype on real data, and build production milestones. Each phase transition is gated and resumable.

How do I write records to a custom Fulcra data type?

Use `fulcra record <Base>/<definition-uuid>` from the CLI, which handles the sources entry for you. With the library or raw REST, POST to the base type endpoint and name the definition in the record's sources array — using the definition UUID as a URL path segment returns 404.

Can a Fulcra prototype use mock or sample data?

No. The skill mandates binding to the user's real Fulcra data discovered via `fulcra catalog`, and creating custom data types for novel streams. A prototype on fixtures is recorded as a FAIL on the real-data binding verification item.

What happens if fde-engine is not installed?

The skill degrades gracefully: you reproduce the canonical engagement file layout manually with `fulcra file` commands, editing the engagement state frontmatter by hand. Resume determinism is reduced and the user is warned.

Does Fulcra support cross-user data sharing for multi-tenant products?

Cross-user datashare is unreleased, so single-account designs with namespaced paths are permitted as a fallback. The architecture document must include a path-to-user-owned section describing migration once datashare ships.