From itteam
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/itteam:new-project-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Activate when Shay indicates a new client engagement is starting and needs a workspace. Trigger phrases: "new project for [client]", "set up a project for [client]", "initialize the [client] project", "scaffold [client]", "create [client] workspace".
Activate when Shay indicates a new client engagement is starting and needs a workspace. Trigger phrases: "new project for [client]", "set up a project for [client]", "initialize the [client] project", "scaffold [client]", "create [client] workspace".
Do NOT activate for:
Projects\ are a different workflow)D:\Claude-Cowork\Projects\Per Global Instructions, plan-then-execute. Creating a new project = 15 new folders + 3 new files. That's enough surface area to warrant a plan and approval before writing.
D:\Claude-Cowork\00_Context\working-preferences.md — naming conventionsD:\Claude-Cowork\Projects\Clalit-Maya-BPSDTracker\ — canonical reference structureProjects\ directory listing — to confirm:
ITTeam projects follow Client-EngagementName format where multiple engagements share a client. The pattern adapts to the situation:
The client has only one ITTeam engagement (current or planned).
<ClientName>Wolt, StraussProjects\The client has (or will have) more than one distinct engagement with ITTeam.
<ClientName>-<EngagementName>Clalit-Maya-BPSDTracker, Clalit-CommandCenter, Clalit-Meshi-ConversationalSupportThe engagement has a specific division, product, or sub-context worth encoding in the name.
<ClientName>-<Division>-<Function> or <ClientName>-<Product>-<Function>Clalit-Meshi-ConversationalSupport, Clalit-Maya-BPSDTracker-), not spaces, not underscoresBPSDTracker not bpsd-tracker)When Shay says "set up a new project for X":
Wolt. Confirm before creating.Projects\ start with the proposed client name? If yes, this is a multi-engagement client — confirm naming with Shay even if Case 1 was initially proposed.D:\Claude-Cowork\Projects\<proposed-name>\. If it exists, stop and ask whether to use the existing folder or pick a different name.D:\Claude-Cowork\Projects\<FolderName>\List every folder to be created:
Projects\<FolderName>\Projects\<FolderName>\00_Project-Context\Projects\<FolderName>\01_Inputs\Projects\<FolderName>\01_Inputs\meetings\Projects\<FolderName>\01_Inputs\client-docs\Projects\<FolderName>\01_Inputs\research\Projects\<FolderName>\02_Working\Projects\<FolderName>\03_Deliverables\Projects\<FolderName>\03_Deliverables\PRD\Projects\<FolderName>\03_Deliverables\SOW\Projects\<FolderName>\03_Deliverables\Proposals\Projects\<FolderName>\03_Deliverables\Decks\Projects\<FolderName>\03_Deliverables\Spreadsheets\Projects\<FolderName>\03_Deliverables\SecurityArtifacts\Projects\<FolderName>\04_Knowledge-Base\Projects\<FolderName>\05_Meetings\Total: 15 folders (project root + 14 subfolders).
00_Project-Context\ — brief, decisions log, glossary (project's identity files)01_Inputs\ — raw source materials, organized by type02_Working\ — drafts and WIP (Cowork's sandbox)03_Deliverables\ — finalized outputs, organized by deliverable type
PRD\ — Product Requirements DocumentsSOW\ — Statements of WorkProposals\ — pre-engagement proposalsDecks\ — presentation filesSpreadsheets\ — data tables, financial models, control matricesSecurityArtifacts\ — security-specific deliverables that don't fit other categories: threat models, security architecture documents, control matrices, security task lists, audit handouts, penetration test reports. Standard for ITTeam engagements given the agency's infosec focus.04_Knowledge-Base\ — synthesized insights, patterns, reusable knowledge from the engagement05_Meetings\ — meeting summaries (named YYYY-MM-DD_topic.md)project-brief.md: 13 numbered sections per the canonical structure. All TBD-fillable sections marked TBD — to be filled at kickoff. Section 1 metadata pre-filled:
Two seed assumptions:
If multi-engagement (Case 2 or 3): add A-03 noting the relationship to sibling projects under the same client prefix, e.g., "Sibling project at Projects\Clalit-Maya-BPSDTracker\ exists; engagements are distinct (separate SOW, scope) but the client is shared."
decisions-log.md: standard structure — title, "Source of record" line, "How to use" section, repeating block template. Seed entry D-001:
Projects\Clalit-Maya-BPSDTracker\ as canonical reference structureglossary.md: two sections — section 1 titled <ClientName>-specific terms, section 2 titled General terms used in this engagement. Both stubbed TBD — to be filled as terms surface. Standard entry format and cross-reference footer.
Projects\<FolderName>\Bank Hapoalim → BankHapoalim), confirm before creating.Maya), confirm.D:\Claude-Cowork\Projects\: stop. Diagnose (permissions, drive letter, disk full). Report.01_Templates\ — that's a separate operationProjects\ — never. Workspace structure is fixed at the root level.npx claudepluginhub shaybar1/itteam-cowork-plugins --plugin itteamGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.