jterrats.dev
Official@jterratsdev
jterrats.dev provides Salesforce delivery skills covering metadata deployment, org health audits, story refinement, QA evidence, and architecture documentation.
Agent Skills by jterrats.dev
Showing 20 vetted skills indexed across 1 GitHub repositories.
jterratsdevdiagram-export
Create, validate, and export architecture, workflow, and sequence diagrams with visual QA.
jterratsdevprompt-registry
Maintains a commit-tracked register of AI prompts that generated each project artifact.
jterratsdevQA Evidence Pack
Build acceptance-criteria-mapped QA evidence reports with observable outcomes and annotated visual artifacts.
jterratsdevstory-mapping
Generate Jeff Patton user story maps as Markdown, Mermaid PDFs, drawio boards, and Lucidspark boards.
jterratsdevorg-health-assessment
Assess Salesforce org health across security, automation, permissions, licenses, and data volumes.
jterratsdevgenerate-rom
Generate Rough Order of Magnitude effort estimates for backlog stories and epics.
jterratsdevelements-sync
Create Requirements and Stories in Elements.cloud via its REST API.
jterratsdevsf-deploy
Deploy and validate Salesforce metadata using dependency-aware wave deployments and profile retrieval.
jterratsdevproject-knowledge-bootstrap
Scans Salesforce project structure to populate project knowledge files with conventions and architecture.
jterratsdevrefine-story-functionally
Refines user stories with discovery probes and testable Gherkin acceptance criteria.
jterratsdevrecord-adr
Writes ADP-style Markdown ADRs and round-trips them into setup-agents decision records.
jterratsdevtranscription-evidence
Transcribe audio and video files and record transcripts as task evidence.
jterratsdevbacklog-sync
Creates issues in GitHub, GitLab, Jira, Azure DevOps, or Bitbucket from story map markdown.
jterratsdevdecompose
Splits epics and oversized stories into independently deliverable slices recorded in a local backlog.
jterratsdevrefine-story-technically
Refines user stories technically using Salesforce metadata dependency graphs and local backlog persistence.
jterratsdevoclif-plugin-dev
Develop oclif and sf CLI plugins with commands, flags, hooks, and tests.
jterratsdevsf-code-analyzer
Runs static code analysis on Salesforce projects using PMD, ESLint, RetireJS, and CPD engines.
jterratsdevoclif-plugin-development
Implements oclif CLI plugins with TypeScript commands, hooks, manifests, and QA evidence.
jterratsdevchaos-resilience-testing
Design deterministic failure scenarios that validate safe degradation of workflows, APIs, and providers.
jterratsdevStatic Analysis
Runs and interprets local lint, typecheck, secret, dependency, and security scans.
Frequently Asked Questions About jterrats.dev
FAQPage SchemaWhat tasks can I accomplish with jterrats.dev's skills?▼
You can deploy Salesforce metadata with wave deployments, assess org health across security and data volumes, refine stories with INVEST and Gherkin checks, decompose epics, generate ROM estimates, export Mermaid diagrams to Lucidchart or PDF, run PMD/ESLint static analysis, and build QA evidence packs with screenshots and traces.
Who are these skills designed for?▼
The skills target Salesforce delivery roles: Technical Architects, Developers, DevOps engineers, Business Analysts, Project Managers, QA engineers, Admins, and Security profiles. Several skills, like record-adr and refine-story-technically, are explicitly owned by the Technical Architect profile.
How do the backlog and story management skills work in practice?▼
Story maps are generated in Jeff Patton format, refined functionally and technically through ADP phases, then pushed to issue trackers. The backlog-sync skill auto-detects GitHub, GitLab, Jira, Azure DevOps, or Bitbucket from project files, maps fields, and guards against duplicate issues.
What prerequisites or dependencies do these skills require?▼
Elements-sync requires ELEMENTS_API_KEY and ELEMENTS_SPACE_NAME environment variables. Diagram-export uses mermaid-cli for PDF rendering and MCP OAuth for Lucidchart. Sf-deploy relies on @jterrats/profiler and @jterrats/smart-deployment packages. Transcription-evidence requires a file path and task ID as inputs.
How do the skills support release quality and traceability?▼
QA-evidence-pack maps acceptance criteria to screenshots, traces, videos, and API contracts. Prompt-registry logs every prompt that produced an artifact for full traceability. Record-adr captures architecture decisions in Markdown and syncs them to decision records, while sf-code-analyzer enforces code quality gates.