gsd-list-phase-assumptions — for Claude Code gsd-list-phase-assumptions, finally, community, for Claude Code, ide skills, $gsd-list-phase-assumptions, {{GSD_ARGS}}, AskUserQuestion, request_user_input, header

v1.0.0

About this Skill

Ideal for AI agents that need <codex skill adapter. gsd-list-phase-assumptions is an AI agent skill for <codex skill adapter.

Features

<codex skill adapter
A. Skill Invocation
This skill is invoked by mentioning $gsd-list-phase-assumptions.
Treat all user text after $gsd-list-phase-assumptions as {{GSD ARGS}}.
If no arguments are present, treat {{GSD ARGS}} as empty.

# Core Topics

lalitnayyar lalitnayyar
[0]
[0]
Updated: 4/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
8/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

Ideal for AI agents that need <codex skill adapter. gsd-list-phase-assumptions is an AI agent skill for <codex skill adapter.

Core Value

gsd-list-phase-assumptions helps agents <codex skill adapter. FinAlly AI Trading Workstation <codex skill adapter A. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Ideal Agent Persona

Ideal for AI agents that need <codex skill adapter.

Capabilities Granted for gsd-list-phase-assumptions

Applying <codex skill adapter
Applying A. Skill Invocation
Applying This skill is invoked by mentioning $gsd-list-phase-assumptions

! Prerequisites & Limits

  • Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
  • Requires repository-specific context from the skill documentation
  • Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is gsd-list-phase-assumptions?

Ideal for AI agents that need <codex skill adapter. gsd-list-phase-assumptions is an AI agent skill for <codex skill adapter.

How do I install gsd-list-phase-assumptions?

Run the command: npx killer-skills add lalitnayyar/finally/gsd-list-phase-assumptions. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for gsd-list-phase-assumptions?

Key use cases include: Applying <codex skill adapter, Applying A. Skill Invocation, Applying This skill is invoked by mentioning $gsd-list-phase-assumptions.

Which IDEs are compatible with gsd-list-phase-assumptions?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for gsd-list-phase-assumptions?

Output: Conversational output only (no file creation) - ends with "What do you think?" prompt. Requires repository-specific context from the skill documentation. Works best when the underlying tools and dependencies are already configured.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add lalitnayyar/finally/gsd-list-phase-assumptions. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use gsd-list-phase-assumptions immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

gsd-list-phase-assumptions

FinAlly AI Trading Workstation <codex skill adapter A. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows. <codex skill adapter

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-list-phase-assumptions.
  • Treat all user text after $gsd-list-phase-assumptions as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective> Analyze a phase and present the agent's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.

Purpose: Help users see what the agent thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective>

<execution_context> @/home/lnayyar/projects/CourseAIVibeCodeUdmey/finally/.codex/get-shit-done/workflows/list-phase-assumptions.md </execution_context>

<context> Phase number: {{GSD_ARGS}} (required)

Project state and roadmap are loaded in-workflow using targeted reads. </context>

<process> 1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow list-phase-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps </process>

<success_criteria>

  • Phase validated against roadmap
  • Assumptions surfaced across five areas
  • User prompted for feedback
  • User knows next steps (discuss context, plan phase, or correct assumptions) </success_criteria>

Related Skills

Looking for an alternative to gsd-list-phase-assumptions or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer