npx claudepluginhub richfrem/agent-plugins-skills --plugin agent-scaffoldersThis skill is limited to using the following tools:
acceptance-criteria.mdevals/evals.jsonevals/results.tsvfallback-tree.mdreferences/acceptance-criteria.mdreferences/advanced.mdreferences/fallback-tree.mdreferences/hitl-interaction-design.mdreferences/migration.mdreferences/pattern-decision-matrix.mdreferences/patterns.mdreferences/patterns/action-forcing-output-with-deadline-attribution.mdreferences/patterns/adversarial-objectivity-constraint.mdreferences/patterns/anti-pattern-vaccination.mdreferences/patterns/anti-symptom-triage.mdreferences/patterns/artifact-embedded-execution-audit-trail.mdreferences/patterns/artifact-generation-xss-compliance-gate.mdreferences/patterns/artifact-lifecycle.mdreferences/patterns/artifact-state-interrogative-routing.mdreferences/patterns/asynchronous-benchmark-metric-capture.mdExecutes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Follow the create-hook skill workflow to design and generate a hook configuration.
$ARGUMENTS — optional hook event type (e.g. PreToolUse, Stop, PermissionRequest)
or a use-case description (e.g. "block dangerous bash commands"). Omit for discovery.$ARGUMENTS names an event or use case, use it to seed Phase 1 questionsvalidate_hook_schema.py and test with test_hook.pyhooks.json vs skill-scoped frontmatter) and next stepshooks.json entry or SKILL.md frontmatter block with complete hook configuration
(event, matcher, handler type, command/prompt body, output schema).
$ARGUMENTS is empty: begin with the event selection question in Phase 1