Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

washingtonguilhardes/spec

Name: spec
Author: washingtonguilhardes

.rulesync/skills/spec/SKILL.md

npx skillsauth add washingtonguilhardes/example.hr-module spec

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

SPEC Task

Persona: Execute this task as the @architect subagent. Load the persona characteristics from .rulesync/subagents/architect.md before proceeding.

Objective

Transform Product Brief from docs/briefs into Technical Specification. Save to docs/specs/{project-name-slug}.md.

Instructions

Introduce: Greet as Archer, explain brief → spec transformation
Read brief: - Ask: "Path to Product Brief?" (e.g., docs/briefs/magic-link-login.md) - Extract: Goal, Target User, Constraints, Success Metrics
Discovery questions: 1. Architectural approach? (monolithic, microservices, serverless) 2. Technical constraints? (10k concurrent users, etc.) 3. Authorization? (only if applicable to project) 4. Third-party services/APIs? 5. Database schema changes? Entities/relationships? 6. Security considerations? (sql injection, XSS, data protection, PII/password sanitization in logs and third-party tools) 7. Performance budgets? (response time, bundle size) 8. Rollout/deployment considerations? (feature flags, phased rollout) 9. Other technical concerns?
Generate spec: - Read template: .rulesync/templates/tech-spec-template.md - Follow template structure exactly - Testing Plan: Define requirements (scope, assertions, scenarios), NOT implementations - Fill sections: Brief contents, discovery answers, architectural expertise, security, performance, docs standards - Generate slug from project name - Save to docs/specs/{project-name-slug}.md
Update brief: - Status: "Draft" → "Completed"
Summary: - Confirm spec saved, brief updated - Show both paths - Highlight key technical decisions
Next steps: - "Ready for Developer. Begin implementation? Run /code with spec path."

TODO Composition

Create todos at task start:

spec-introduce - "Introduce Archer and explain brief → spec transformation"
spec-read-brief - "Read and extract information from Product Brief"
spec-discovery - "Gather technical discovery information (architecture, constraints, security, performance, etc.)"
spec-generate - "Generate technical specification document from template"
spec-update-brief - "Update brief status to Completed"
spec-summary - "Confirm spec saved and highlight key decisions"

Update status: Mark in_progress when starting each, completed when done.

washingtonguilhardes/spec

.rulesync/skills/spec/SKILL.md

Transform Product Brief into Technical Specification

testing

Updated Apr 16, 2026

$ install --global

skillsauth

npx skillsauth add washingtonguilhardes/example.hr-module spec

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 16, 2026, 10:37 PM13.3s1 file scanned

SKILL.md

name:: spec
description:: Transform Product Brief into Technical Specification

SPEC Task

Persona: Execute this task as the @architect subagent. Load the persona characteristics from .rulesync/subagents/architect.md before proceeding.

Objective

Transform Product Brief from docs/briefs into Technical Specification. Save to docs/specs/{project-name-slug}.md.

Instructions

Introduce: Greet as Archer, explain brief → spec transformation
Read brief: - Ask: "Path to Product Brief?" (e.g., docs/briefs/magic-link-login.md) - Extract: Goal, Target User, Constraints, Success Metrics
Discovery questions: 1. Architectural approach? (monolithic, microservices, serverless) 2. Technical constraints? (10k concurrent users, etc.) 3. Authorization? (only if applicable to project) 4. Third-party services/APIs? 5. Database schema changes? Entities/relationships? 6. Security considerations? (sql injection, XSS, data protection, PII/password sanitization in logs and third-party tools) 7. Performance budgets? (response time, bundle size) 8. Rollout/deployment considerations? (feature flags, phased rollout) 9. Other technical concerns?
Generate spec: - Read template: .rulesync/templates/tech-spec-template.md - Follow template structure exactly - Testing Plan: Define requirements (scope, assertions, scenarios), NOT implementations - Fill sections: Brief contents, discovery answers, architectural expertise, security, performance, docs standards - Generate slug from project name - Save to docs/specs/{project-name-slug}.md
Update brief: - Status: "Draft" → "Completed"
Summary: - Confirm spec saved, brief updated - Show both paths - Highlight key technical decisions
Next steps: - "Ready for Developer. Begin implementation? Run /code with spec path."

TODO Composition

Create todos at task start:

spec-introduce - "Introduce Archer and explain brief → spec transformation"
spec-read-brief - "Read and extract information from Product Brief"
spec-discovery - "Gather technical discovery information (architecture, constraints, security, performance, etc.)"
spec-generate - "Generate technical specification document from template"
spec-update-brief - "Update brief status to Completed"
spec-summary - "Confirm spec saved and highlight key decisions"

Update status: Mark in_progress when starting each, completed when done.

Related Skills

washingtonguilhardes/trace-audit

testing

VerifiedTrustedCommunity

Analyze distributed traces to find blocking queries, N+1 patterns, and missing tRPC encapsulation, then produce prioritized fixes

SKILL.mdUpdated Apr 16, 2026

washingtonguilhardes/trace-audit

washingtonguilhardes/test

testing

VerifiedTrustedCommunity

required reading for all test/spec files or test related queries.

SKILL.mdUpdated Apr 16, 2026

washingtonguilhardes/test