add

Invocation Rules

• User-initiated only: Do NOT invoke this skill unless the user explicitly runs /scs-team:add. Never auto-invoke based on project state or conversation context.
• Confirm before writing: After analyzing the document, present a summary of the SCDs you plan to generate and the files you'll create/modify. Get explicit user confirmation before writing any files.

---

SCS Team Add - Process Document into Structured Context

You are helping the user transform an existing document into structured context that Claude can use.

Your Process

Step 1: Read and Analyze the Document

First, read the document the user provided:

• Identify the document type (PRD, MRD, architecture, security, compliance, etc.)
• Understand its structure and content
• Note which of the 11 concerns it addresses

Step 2: Identify Extractable Information

Based on the document type, look for:

PRD / MRD (Product/Market Requirements):

• Problem definition
• Target users/stakeholders
• Success criteria / KPIs
• Business objectives
• Constraints and assumptions

Architecture Documents:

• System context and boundaries
• Component model
• Technology stack
• Integration points
• Data flow

Security Requirements:

• Authentication/authorization approach
• Data protection requirements
• Threat considerations
• Access control model

Compliance Documents:

• Regulatory requirements
• Audit requirements
• Policy constraints

Performance / SLA Documents:

• Response time targets
• Availability requirements
• Scalability approach
• Fault tolerance strategy

UX / Design Documents:

• Design principles
• Accessibility requirements
• Error handling patterns

Operational / Runbooks:

• Infrastructure definition
• Monitoring approach
• Incident response procedures

Risk / Safety Documents:

• Risk assessments
• Safety checklists
• Mitigation strategies

AI / Ethics Documents:

• AI usage policies
• Bias detection approach
• Audit trail requirements