gtsi-execute

Generates authorized operational artifacts like templates, checklists, scripts, and ticket models incrementally.

Updated May 21, 2026
One-click install
npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-execute-gestaosian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtsi-execute
Source: https://github.com/gestaosian/gtsi-claude-skills/tree/main/plugins/gtsi-ops-plugin/skills/gtsi-execute
Command: npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-execute-gestaosian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved plan into concrete deliverables often stalls because teams lack ready-made templates, structured ticket models, or a safe way to execute step by step without risking destructive changes. ## Core Features & Use Cases - Artifact Generation: Produces files, markdown documents, templates, checklists, spreadsheets, scripts, directory structures, and backlog examples from an authorized plan. - Incremental Safe Execution: Executes in small visible steps, explains impact and limitations upfront, and requires explicit confirmation before any destructive action. - Governance Redirection: When execution depends on real system access, permissions, or infrastructure changes, it prepares the Freshworks/Freshservice ticket model, functional description, and acceptance criteria instead of inventing access. - Use Case: After approving a plan to standardize operational procedures, ask it to generate the POP templates and the project folder structure, then receive a ticket model for the access request that requires GTSI support. ## Quick Start Authorize execution after a plan by saying: yes, proceed with the plan and generate the suggested templates and folder structure.

Frequently Asked Questions about gtsi-execute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an operational plan with Claude Code?▼

Explicitly authorize execution after a plan, for example by saying "yes, proceed". The skill then lists what will be executed, its limitations, and produces artifacts incrementally in small visible steps with file paths for each result.

What artifacts can an execution assistant generate from a plan?▼

It generates files, markdown documents, templates, checklists, spreadsheets, presentations, scripts, directory structures, backlog examples, and Freshworks ticket models with functional descriptions and acceptance criteria.

Can Claude execute changes in corporate systems directly?▼

No. It never assumes access to corporate systems, credentials, or infrastructure. When execution depends on permissions or system changes, it prepares the ticket model and directs the user to open a request with GTSI via Freshworks/Freshservice.

How are destructive actions handled during assisted execution?▼

Destructive actions such as overwriting, deleting, or altering important files require explicit user confirmation before proceeding. The skill explains expected impact and limitations upfront and refuses irreversible actions without confirmation.

What happens if I invoke execution without an approved plan?▼

Without explicit authorization, the skill refuses to execute and redirects to the gtsi-plan skill or asks for authorization first. Execution mode only activates after clear user approval of a defined plan.