
Factory Human Digest
Experimental workflow for summarizing work that still needs human judgment across...
Install
npx skills add BuilderIO/skills --skill factory-human-digest -g -a claude-code -y- Repository
- BuilderIO/skills4.6k
- Category
- Engineering
- Updated
- 7d ago
- License
- MIT
- Context cost
- Lightabout 907 tokens
- Runs scripts
- No, instructions only
What it does
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
Factory Human Digest
Start with the Factory guide for workflow setup and configuration.
Read .agent-factory/config.yaml and apply the optional
skill_prompts.factory-human-digest entry as additional project guidance.
Inspect only the repositories and sources it authorizes.
Choose the scope
For a manual run with no narrower request or workflow settings, include all
configured source categories, use the last 7 days, and report at balanced
granularity. A user can narrow or expand the request in ordinary language, for
example, “PRs only, last 30 days, detailed” or “everything from this week, brief.”
Use configured repository and source boundaries even when the requested time
window or category changes. For scheduled runs, use
workflows.human-digest from the config.
Categories can include pull requests, issues, feedback, errors, telemetry, and stalled or failed delivery work. A category filter selects records to inspect; it does not expand access to another project or integration.
Find items that need a person
Read configured sources and repositories completely for the selected window. Follow pagination and record the actual dates, filters, counts, and any source that was unavailable or truncated. Include items held outside the normal agent-handled flows, such as:
- pull requests waiting for human review, approval, a merge decision, or product judgment;
- issues, feedback, or errors held for missing context, unclear intent, risk, conflicting evidence, or a decision outside the configured automation rules;
- new answers to information requests that have not yet been re-triaged;
- recurring incidents, UX concerns, or delivery work that stopped without a verified resolution or safe authorized next step.
