uashogeschoolutrecht/hu-core

Reduce material uncertainty before specification when a HU project is big, risky, ambiguous, or likely to cause substantial rework. Invoked by get-started after quick alignment; not a standalone entry point.

Establish the minimum shared understanding needed to start a HU project safely without creating unnecessary questioning friction. Invoked by get-started; not a standalone entry point.

Execute dependency-aware HU task files in human-approved, bounded waves using tightly scoped VS Code sub-agents. Use only when task files and an execution policy already exist; get-started invokes this when the policy enables sub-agents.

Explain HU rules for data, models, and external endpoints. Use when a project handles data or chooses an AI model or external service.

Start or continue a HU project using a risk-aware, spec-driven development workflow. Use when beginning a project, adding a feature, or asking how to run project work with the HU framework. For authoring or sharing a skill or agent, use make-skill, make-agent, or share-contribution instead.

Find and apply reviewed HU-wide knowledge before making development decisions, especially for HU terminology, organizational context, standards, templates, and common solution patterns.

Create a custom HU agent with a narrow role and an explicit tool allowlist. Use when a reusable role needs its own tool permissions or its own context, and a skill cannot express it.

Create a new HU skill, or improve an existing one, so it follows the framework's structure and triggers reliably. Use when the user wants to turn a repeated prompt, workflow, or piece of know-how into a reusable skill.

Turn an agreed HU specification into small, dependency-aware task files with local tests and intermediate vertical-slice validation tasks. Use when an agreed specification already exists; get-started invokes this at its decomposition stage.

Capture and sharpen the constraints and preferences underneath a user's stated goal into project principles, and apply them to design and implementation choices. Use during deep alignment, when the user gives evaluative feedback on a decision or design, or when they ask what the project stands for.

Check a skill or agent against the HU framework standard and prepare a reviewed pull request to share it with the team or university. Use when the user asks to share, contribute, publish, or promote a skill or an agent.