| name | haipipe-project |
| description | Quick project setup: create the container folders and stop. Two kinds by name: Project-* = repo-backed (gh repo under a user-chosen org, never assumed; submodule at examples/<name>; if the repo already exists, adopt and pull it) and ProjX-* = plain directory under examples/. Owns ONLY the container layout (tasks/ discoveries/ papers/ applications/ diagram/; probes/ retired 2026-07-05 and insights/ retired 2026-07-12 — a paper's evidence questions live in its own 1-probes/ PPNN probe files, and the bank answers them in <task-folder>/QA/<n>-<slug>.md); each subfolder's internals belong to its owning skill family. Task/run scaffolding lives in /haipipe-task. Trigger: new project, project scaffold, repo project, project submodule, /haipipe-project. |
| argument-hint | [repo|new|feedback|digest] [Project-Name|args...] |
| allowed-tools | Bash, Read, Write, Edit, Grep, Glob, Skill |
| metadata | {"version":"0.3.4","last_updated":"2026-08-05","summary":"Project SETUP only: Project-* repo-backed submodules + ProjX-* plain dirs. Everything else moved out or retired. v3.2 syncs the container contract to the probe v3 model (Tools/plugins/haipipe-toolkit/diagram/260714-probe-qa/, JL 2026-07-14): a task/discovery LEAF may carry an OPTIONAL QA/ folder (QA/<n>-<slug>.md — the executor's readable digest, numbering IS the index, on BOTH banks); the scaffold NEVER mints _ASK/ or _ANS/ (the bank is PROBE-UNAWARE: no PP ids, no answers: field); a consumer's evidence questions live in papers|applications/<X>/1-probes/PPNN_<topic>/ (renamed from 1-probe-plans/), bound to the bank BY PATH."} |
Skill: haipipe-project (project setup)
One job: set up a well-formed project container, QUICKLY. Setup = folders ready (plus README + .gitignore for the repo kind) and stop. No metadata questionnaire, no diagram authoring, no seed tasks -- those are on-request extras. The name decides the kind:
/haipipe-project repo <Project-Name> [--org <owner>]
REPO-BACKED project (fn/repo-project.md)
gh repo create <org>/<name> --private
+ submodule at examples/<name>
+ scaffold + push + workspace pointer bump
papers inside are submodules OF THE PROJECT
org resolved per invocation (flag or ask;
NO default org -- skill serves many owners)
/haipipe-project new <ProjX-Name> PLAIN-DIRECTORY project (fn/project.md)
examples/<ProjX-Name>/ container folders (papers/ etc.)
/haipipe-project feedback "<text>" capture skill feedback (merge-or-create)
/haipipe-project digest [session] [--dry-run] harvest feedback from a transcript
/haipipe-project list projects under examples/ + the two setup paths
Not this skill's job (where it lives instead):
task-group / task-folder / run scaffolding -> /haipipe-task (task/)
eval status scanning (scan-status) -> /haipipe-task (task/)
workflow plan/report schema -> task/haipipe-workflow
paper folders inside a project -> /haipipe-paper folder
project audits / reorganization -> retired; originals in project/_archive
claims / evidence questions -> /haipipe-probe (a probe is a
paper-level file, papers/<P>/1-probes/PPNN_<topic>/
-- it owns NO folder in the execution tree)
asking the bank a question -> /haipipe-task qa · /haipipe-discovery qa
Container Layout + Structure Ownership
This skill owns ONLY the top-level container. Each subfolder's INTERNAL structure is owned by its skill family; when setup or a question needs the details, CONSULT (infer from) the owner listed below -- never restate its rules here.
📦 examples/<name>/ (this skill sets up the container)
├── ⚙️ tasks/ owner: /haipipe-task two-level hierarchy, group letters, task-folder anatomy
├── 🔎 discoveries/ owner: /haipipe-discovery one topic = one folder (Search / Review / Idea types)
├── 📄 papers/ owner: /haipipe-paper-* paper-folder contract (paper wiki); each paper a submodule (legacy projects use singular paper/; do not migrate)
├── 📬 applications/ owner: /haipipe-application-* non-academic deliverables
└── 🗺️ diagram/ owner: this skill (via /diagram-ascii) 01-story, 02-boundary -- EMPTY at setup, authored on request
