nsantini

@nsantini source repo

9 skills
0 followers
8 hours ago last updated

▌
Gsdl · nsantini bundle
GSDL (Get Shit Done Light) orchestrator. Runs the full pipeline: pick up the work item → brainstorm → SPEC.md → decompose into slices → human review → branch → execute → verify gates → open PR and address review-bot findings → close loop with evidence. Use when the user wants to build something end-to-end, says "let's GSD", "run the GSDL pipeline", "pick up this ticket", or wants the full workflow. Coordinates gsdl-fetch-source, gsdl-create-spec, gsdl-decompose, gsdl-execute, gsdl-verify-gates, gsdl-open-pr, gsdl-close-loop, and gsdl-tracker-sync. Works with any issue tracker (Linear, Jira, GitHub Issues, Notion) or none at all, and with any model provider. Can be invoked from ANY session model — it routes each step to that step's capability tier. Accepts a work-item URL/ID, a doc URL, a plain idea, or an existing project name to resume: /gsdl [url|id] OR /gsdl [project-name] OR /gsdl [idea].

0
installs
▌
Gsdl Execute · nsantini
Execute tasks.md step-by-step with completion tracking, committing to git and updating the corresponding tracker sub-item as each slice completes. Use when the user wants to work through a plan, implement tasks sequentially, or asks to "execute the plan" or "start implementing". This is Step 6 (Execute) of the GSDL pipeline. Runs on the MEDIUM tier.

0
installs
▌
Gsdl Open Pr · nsantini
Push the working branch, open a GitHub pull request for the project, then wait for the repo's automated code-review bot (Cursor BugBot, CodeRabbit, Copilot, Greptile, or whichever is installed) and address its findings. Use when implementation and gates are done and the change needs a PR, or when the user asks to open a PR, check bot review comments, or address automated review feedback. This is Step 8 (Open PR + Address Review Bot) of the GSDL pipeline. Runs on the MEDIUM tier.

0
installs
▌
Gsdl Decompose · nsantini
Break SPEC.md down into implementable slices, write tasks.md, and create one tracker sub-item per slice when a tracker is configured. Use when the user wants to decompose a spec into tasks, break a plan into sub-issues, or create a task list from SPEC.md. This is Step 4 (Decompose into Slices) of the GSDL pipeline. Slicing runs on the LARGE tier; the tracker writes are delegated to the SMALL tier via gsdl-tracker-sync.

0
installs
▌
Gsdl Close Loop · nsantini
Capture decisions, architecture changes, gate evidence, and PR review outcomes from a project into a structured document, then close the corresponding tracker item with that evidence attached and optionally publish the document to Slite, Notion, or Confluence. Use when the user wants to wrap up a project, document what was built, or close out a ticket. This is Step 9 (Close Loop with Evidence Captured) of the GSDL pipeline — the final checkpoint. Synthesis runs on the LARGE tier; the tracker writes are delegated to the SMALL tier via gsdl-tracker-sync.

0
installs
▌
Gsdl Create Spec · nsantini bundle
Generate SPEC.md from a seed file or user input. Use when the user wants to produce a plan, write a spec, document requirements, formalize a feature, or turn an idea/ticket/doc into a structured plan. This is Step 3 (Produce a Plan) of the GSDL pipeline — its output IS the checkpoint. Runs on the LARGE tier.

0
installs
▌
Gsdl Fetch Source · nsantini
Pick up the starting point for a GSDL project — a tracker work item (Linear, Jira, GitHub Issues, Notion), a specification document (Notion, Slite, Confluence), or a plain idea with no tracker at all — and create .planning/[project-name]/ with seed.md populated from it. Also establishes the workspace provider config on first run. Use when the user gives a ticket URL/ID, a doc URL, or an idea as the starting point for a project, or asks to 'pick up this ticket'. This is Step 1 of the GSDL pipeline. Runs on the SMALL tier.

0
installs
▌
Gsdl Tracker Sync · nsantini
Perform issue-tracker writes for GSDL against whichever tracker is configured — Linear, Jira, GitHub Issues, Notion, or none (local markdown). Creates sub-items under a parent work item, comments on items, and transitions item status. Use when a GSDL step needs to push something to the tracker: sub-item creation at decompose time, slice completion at execute time, or item closure at close-loop time. Mechanical API work only: it never decides what to write, only writes what it is given. Runs on the SMALL tier.

0
installs
▌
Gsdl Verify Gates · nsantini
Run the project's deterministic checks (tests, lint, typecheck, build) and produce a pass/fail gate report before opening a PR or closing out. Use when the user wants to verify a change, run the test suite before wrapping up, check gates, or asks "are we good to close this out?". This is Step 7 (Verify Against Deterministic Gates) of the GSDL pipeline. Runs on the MEDIUM tier.

0
installs

9 published skills