Add Community TaskAdd Community Task v1.0.1

Add Community Task is for contributors who want to publish a HagiTask Community Task without hand-assembling a dozen interlocking files. A Community package is a manifest, a panel, a task preset, a prompt package, per-locale templates, locale bundles, and per-locale store pages — and every one of those has to agree with the others. Miss one and the validator rejects the package; get one subtly wrong and it ships broken.

This task front-loads the format into the panel and the prompt, then carries the contribution all the way to a pull request.

What it does

Collects one complete brief before generating anything

The panel provides one required multiline brief for the objective, user value, input constraints, execution and quality rules, acceptance criteria, and optional publication notes. The prompt extracts and structures that continuous explanation before generating the package, so authors do not have to split one idea across multiple text boxes.

Writes only inside your fork

Repository, vault, and project selections are read-only context. The executor resolves the upstream repository from its public GitHub URL, reuses your existing fork or creates one with gh, works in a temporary checkout, and writes only under data/<task-id>/ on a working branch. Nothing writes to the repositories you attached, and nothing writes to the installed HagiTask CLI dependency.

Treats validation as a completion condition

After generating the package the executor runs the repository’s own npm run validate and npm test using the installed CLI. It reports the real exit status. Editing generated output or dropping an error to make the run look clean is explicitly forbidden.

Finishes the contribution

Once validation passes, the executor commits to the working branch, pushes to your fork, and opens a pull request against the upstream default branch with gh pr create. The result reports the fork, the branch, the validation outcome, and the pull request URL. If authentication fails or the fork cannot be created, the task stops with diagnostics instead of claiming a pull request that does not exist.

Requirements

• gh installed and authenticated (gh auth status must pass)
• git and Node.js available in the execution environment
• A GitHub account that can fork the upstream Community Packages repository

Best fit

• Best for: publishing a new Community Task, and doing it end to end from brief to pull request.
• Also good for: learning the package format by generating a correct one and reading the diff.
• Not for: editing an already-published package, changing HagiTask schemas, or modifying the site build.

FAQ

Does it write to the repositories I select in the panel?

No. Repository selection is read only. It exists so the executor can consult your code as reference when shaping the new task. The single write scope is data/<task-id>/ in a branch of your fork.

What if I already have a fork of the Community Packages repository?

It is reused. The executor checks for an existing fork with gh repo view before calling gh repo fork, so you do not end up with duplicates.

Does a passing validation mean the package is ready to merge?

No. The validator checks structure: schemas, canonical ids, declared paths, locale coverage, template resolution, and store-page frontmatter. It does not judge whether the prompt text is coherent, whether both locale bundles carry the same keys, or whether the store page describes real behavior. The task reports those as manual review items, and a human reviewer still owns the merge decision.