Stats
Actions
Available In
Tags
Plugin
itteam
ITTeam plugin — ITTeam-specific workflows for project setup, deliverable finalization, meeting documentation, and decision logging. Enforces PPT methodology, plan-then-execute discipline, stable IDs, and branded output standards.
What's Inside
Slash Commands2
/finalize
/finalize
Finalize a markdown draft as a branded ITTeam .docx deliverable. Invokes the finalize-branded-docx skill. Optional argument: path to the source markdown file.
/log
/log
Log a decision to the current project's decisions-log.md with the next stable ID. Invokes the log-decision skill. Optional argument: the decision statement itself. Only for decisions already made — not for tentative or future decisions.
Skills4
finalize-branded-docx
/finalize-branded-docx
Use this skill when Shay says "finalize", "publish", "produce branded version", "make this a deliverable", or asks to convert a final markdown draft into a branded ITTeam Word document. Use when the user references producing a final .docx of a PRD, SOW, Proposal, Meeting summary, or any document that needs ITTeam header/footer/logo branding. Do NOT use for non-final drafts, in-chat content, or non-Word formats. This skill is the markdown-to-branded-docx workflow defined in 00_Context\brand-identity.md.
log-decision
/log-decision
Use this skill when Shay states a decision has been made AS A COMPLETED ACT and asks to log, record, or capture it in the project's decisions log. Trigger phrases include "log this decision", "record this decision", "we decided X", "we agreed on Y — log it", "capture this in the decisions log", or the /log slash command. Do NOT use for tentative, hedged, future-tense, or in-progress decisions ("probably", "thinking about", "leaning toward", "I think we're going with", "we'll probably", "tomorrow we'll decide"). The decision must be stated as already made, in past or present-perfect tense, not as a forecast or preference.
Meeting summary from notes
/meeting-summary-from-notes
Activate when Shay provides raw meeting material — handwritten notes, typed notes, Zoom/Teams transcript, voice-memo transcription, or pasted bullets — and asks for a properly structured ITTeam meeting summary.
new-project-setup
/new-project-setup
Use this skill when Shay asks to set up, create, initialize, or scaffold a new ITTeam project. Trigger phrases include "new project for [client]", "set up a project for [client]", "create the [client] project", "scaffold [client]", "initialize [client] workspace". This skill creates the standard 15-folder project structure under D:\Claude-Cowork\Projects\<name>\ following ITTeam's naming conventions (single-engagement clients use Client; multi-engagement clients use Client-Engagement) and seeds the three 00_Project-Context files (project-brief, decisions-log, glossary). Do NOT use to modify existing projects or to create folders outside the Projects\ tree.
Stats
Version1.0.2
Stars0
MaintenanceGood
LicenseProprietary — ITTeam internal use only
Last Commit
Added
Available In
Tags
Categories
