Enqueue PRD files or inline descriptions for the eforge daemon to build.
npx skills add https://github.com/eforge-build/eforge --skill eforge-build
Please help me install this Agent Skill. Skill: eforge-build Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-build Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-build
Enqueues a PRD file or inline description for the eforge daemon to build, enabling engineers to hand off planning, execution, and validation to a guided, repeatable pipeline without manual reformatting.
Provide a PRD file path or inline description and run /eforge:build to enqueue a build.
High-intent search queries and answers about installing and using this skill.
To enqueue a PRD file for automated build planning, provide the file path or inline description to the build daemon. The pipeline resolves the source, validates project configuration, and submits the PRD to initiate the build process with progress tracking.
A PRD build pipeline automates planning, execution, and validation by submitting product requirement documents to a build daemon. You need it when handing off complex build tasks to a guided, repeatable pipeline without manual reformatting.
Yes, you can submit an inline description or summarized conversation context instead of a PRD file. The build daemon resolves multiple input sources including file paths, inline text, or active planning sessions, routing them into the build pipeline.
Validating project configuration before enqueuing a build happens automatically when you submit your PRD or inline context. The daemon checks the configuration, resolves sources, and updates session state with a sessionId for tracking build progress.
Yes, the build daemon supports active planning sessions and session-status workflows. It can submit ready plans, continue planning when needed, and update session state with resulting sessionIds for ongoing progress tracking throughout the build lifecycle.
A daemon-based build pipeline requires valid project configuration and compatible source inputs. If the PRD file path is inaccessible or the inline context lacks sufficient detail, the daemon may fail to resolve sources or validate the build setup properly.
sinositatoGenerate a first-draft Product Requirements Document from a context file or feature brief.
forcedotcomUpload files from React UI bundles to Salesforce with progress tracking.
JoernStoehlerCoordinate agent collaboration patterns and session handoffs for multi-agent workflows.
iludeAutomate Makefile workflows with PHONY targets, variables, and platform detection.
