Skip to main content

plan-a-group-project

Turn a shared school or student project into agreed scope, fair ownership, milestones, integration checks, and a contribution record without doing graded work for the group. Use when classmates need to divide an assignment, recover a late group project, or make collaboration and accountability visible.

Informations de source

Dépôt
protosphinx/sphinxstack
Dernière activité de la source
29 juillet 2026 à 13:55
Langue détectée de SKILL.md
anglais
Étoiles
3
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers
2 fichiers

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
plan-a-group-project
category
school
description
Turn a shared school or student project into agreed scope, fair ownership, milestones, integration checks, and a contribution record without doing graded work for the group. Use when classmates need to divide an assignment, recover a late group project, or make collaboration and accountability visible.
# plan-a-group-project Create one shared plan that makes dependencies, decisions, and contribution visible. Keep the students responsible for the academic work while helping them coordinate and verify it. ## Inputs - Obtain the assignment, rubric, deadline, required format, group members, accessibility needs, and course rules. - Ask what work already exists, what each member can own, and when people are actually available. - Confirm the allowed use of AI, external sources, peer editing, and shared documents. ## Procedure 1. Read the assignment and rubric together. Translate them into deliverables and observable checks without writing the graded content. 2. Agree on the project's central question, scope, audience, and source-of-truth folder or document. 3. Break deliverables into tasks small enough for one owner and one review point. Mark dependencies and integration work. 4. Assign work by interest, skill, availability, and learning goals. Check that invisible coordination and editing work are not concentrated on one person. 5. Set internal milestones before the official deadline: research complete, rough parts, first integration, feedback, revision, final check, and submission. 6. Define file naming, citation, formatting, decision, and communication rules. Record decisions where all members can see them. 7. Create a contribution log containing task, owner, status, evidence link, review, and blocker. 8. Integrate early. Use the rubric to check consistency of argument, terminology, citations, visuals, and transitions. 9. When a task slips, contact the owner privately, clarify the blocker, resize or reassign transparently, and update the plan. Do not conceal non-participation. 10. Rehearse the final presentation or submission process, including file access, timing, speaking roles, and a backup copy. 11. Hold a short retrospective and preserve an accurate contribution record if the course requests it. ## Boundaries Do not write graded answers, fabricate sources, impersonate a student, or falsify contribution. Do not publish classmates' schedules or private circumstances. Escalate persistent participation or safety issues through the instructor's stated process rather than shaming a member. ## Done - A shared plan maps every rubric deliverable to an owner, milestone, dependency, and evidence link - The contribution log accurately records work, reviews, decisions, blockers, and reassignment - An integrated draft is checked against the rubric before the final deadline - Submission or presentation logistics, permissions, timing, and a backup copy are verified by the group Then use slide-deck for the presentation structure or references-list for a clean source record.
Voir sur GitHub