Forge tasklets — small Cursor operations
Tasklets are single-operation Cursor rules (.mdc) with a fixed output shape. A meta-Versona (for example Sampling Versona) can invoke them in sequence and merge results into a report shaped like a §5 pass or other agreed structure (see VERSONA-CONTRACT.md).
They are not a replacement for discipline Versonas (virtual personas for Product Management, BA, Testing, …). Use tasklets as building blocks and teaching aids.
Full taxonomy (execution plane, operation class, discipline overlay): TASKLET-TAXONOMY.md.
Mental model: layers
Tasklet cognition layers
How single-operation tasklets stack under a meta-Versona that sequences them into a bounded, reviewable report.
- Process flowFrames how cognition tasklets and meta-Versonas relate on this page.
- Lane A ──► handoff ──► shared outcomeSequential tasklet invocations hand outputs toward one merged report shape.
- Lane B ──► inspect / adapt ──► feedbackInspect-and-adapt loops refine tasklet outputs before merge or downstream Versona work.
- Note: `versona-sampling.mdc`Points to the bundled meta-Versona that demonstrates the tasklet sequence.
Process flow
Lane A ──► handoff ──► shared outcome
Lane B ──► inspect / adapt ──► feedback
Note: `versona-sampling.mdc`Install: file flow
Tasklet install file flow
How install-tasklets.sh copies cognition rules into `.cursor/rules/` with optional sampling meta-Versona.
- Process flowFrames what the installer places on disk at repository root.
- Lane A ──► handoff ──► shared outcomeInstaller copies forge-tasklet rules into `.cursor/rules/` as the shared outcome.
- Lane B ──► inspect / adapt ──► feedbackOptional flags and dry-run inspect the install plan before overwriting files.
- Note: `versona-sampling.mdc`Marks the optional meta-Versona copied alongside tasklet rules unless skipped.
Process flow
Lane A ──► handoff ──► shared outcome
Lane B ──► inspect / adapt ──► feedback
Note: `versona-sampling.mdc`Note: versona-sampling.mdc ships with sync-forge-cursor-rules.sh sync --preset recommended (process-first default). This installer adds the forge-tasklet-*.mdc cognition rules; both layers can coexist.
Install (project root)
From a repository that already contains the blueprints/ submodule (run at repository root):
bash blueprints/sdlc/methodologies/forge/tasklets/install-tasklets.sh
Options:
| Flag | Effect |
|---|---|
--dry-run |
Print planned copies only |
--force |
Overwrite existing files in .cursor/rules/ |
--no-sampling |
Install only tasklets; skip versona-sampling.mdc |
Optional target directory (default: current directory):
bash blueprints/sdlc/methodologies/forge/tasklets/install-tasklets.sh /path/to/repo
What gets installed
| Installed file | Purpose |
|---|---|
.cursor/rules/forge-tasklet-extract-assumptions.mdc |
Pull explicit/implicit assumptions from text or context |
.cursor/rules/forge-tasklet-list-unknowns.mdc |
List unknowns, missing evidence, unresolved decisions |
.cursor/rules/forge-tasklet-quick-triage.mdc |
Short severity triage table (max five signals) |
.cursor/rules/forge-tasklet-route-request.mdc |
Suggest @versona-* routing table for a goal + work item |
.cursor/rules/forge-tasklet-bootstrap-session.mdc |
Session folder + SESSION.md frontmatter stub |
.cursor/rules/forge-tasklet-check-standards.mdc |
L1–L6 applicability checklist (not legal advice) |
.cursor/rules/forge-tasklet-log-event.mdc |
Classify event → Ember Log vs SESSION vs versona-track |
.cursor/rules/forge-tasklet-merge-outputs.mdc |
Mechanical merge of pasted tasklet / §5 fragments |
.cursor/rules/forge-tasklet-summarize-evidence.mdc |
Evidence path coverage map for verify/release |
.cursor/rules/versona-sampling.mdc |
Demo meta-Versona that runs the three tasklets and merges output |
Skill matrix (which Versona uses which tasklet): ../versona/VERSONA-SKILL-MATRIX.md.
After install, tune globs: in each .mdc for your repo (defaults are empty = manual / @-rule invocation).
Bundled meta-Versona
See versona-sampling.mdc.template — Sampling Versona demonstrates meta-Versona + tasklets with a simple, readable flow. Install copies it to .cursor/rules/versona-sampling.mdc.
Relationship to execution-plane work
Tasklets in this folder are cognition-plane (in-IDE LLM only). Docker / browser / API steps belong in blueprints/agents/ recipes; a Versona can reference those as execution tasklets with a manifest — see agents/docs/VERSONA-EXECUTION-TASKLETS.md. Tooling split (Rules, AGENTS.md, Skills, subagents, recipes): ../VERSONA-OPERATING-MODEL.md §3. Shared Skills (session, standards, handoff, merge, evidence, diagrams): ../../../templates/forge/cursor-skills/ and ../versona/VERSONA-SKILL-MATRIX.md.
See also
../versona/README.md— Versona catalog../versona/VERSONA-CONTRACT.md— output shape for full discipline Versonas../setup/README.md— Forge adoption andforge-init.sh