2 results for “teamwork”
A full end-to-end hackathon coordination skill. Use this skill whenever a user mentions a hackathon, hack day, build competition, or sprint event — even casually (e.g., "we're doing a hackathon this weekend", "I want to prep for a hackfest", "help us organize our hack team"). This skill guides a solo hacker or team through every phase: intake of hackathon details, team formation, idea collection and selection, GitHub repo setup, task assignment, vibe-coding, presentation prep, and final submission. Works in Claude Code, Claude.ai, and any coding agent that supports skills. Trigger this skill even when the user only mentions one phase (e.g., "help us pick an idea for our hackathon") — always load the full skill to understand context and jump in at the right phase.
Senso's Shared Context path: the organization's memory. It holds the knowledge, policies, procedures and decisions that a team keeps up to date together. Every teammate's agent answers from it with sources, and changes are reviewed and saved as new versions. Use for "Shared Context", "shared context", "what's this org about", "catch me up", "how does this team work", "what do we know about", "what did we decide about", "where is our", "that's wrong, fix it", "update the doc", "save this decision", "ask <name>", "leave <name> a question", "push this to Senso", "what's waiting on me", "what can't our agents answer", "what changed since I last looked", and when the senso-quickstart router sends the user here. Runs senso-shared-context-setup first when the knowledge base is empty. Do not use for the Verification Loop (senso-verification-loop). Do not use for a plain save, lookup or handoff of named material (senso-context-layer).