Skip to content
Back to skills

Thrunt List Phase Assumptions

ASecurity

Surface the agent's assumptions about a phase approach before planning

  • 36 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 28, 2026
ai-agentsgobashgit

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add backbay-labs/thrunt-god --skill thrunt-list-phase-assumptions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Thrunt List Phase Assumptions?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Thrunt List Phase Assumptions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/backbay-labs-thrunt-list-phase-assumptions/badge)](https://www.skillsdirectory.com/skills/backbay-labs-thrunt-list-phase-assumptions)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: thrunt-list-phase-assumptions
description: Surface the agent's assumptions about a phase approach before planning
argument-hint: "[phase]"
allowed-tools: Read, Bash, Grep, Glob
---


<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>
@.github/thrunt-god/workflows/list-phase-assumptions.md
</execution_context>

<context>
Phase number: $ARGUMENTS (required)

Project state and huntmap 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 huntmap
3. Follow list-phase-assumptions.md workflow:
   - Analyze huntmap 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 huntmap
- Assumptions surfaced across five areas
- User prompted for feedback
- User knows next steps (discuss context, plan phase, or correct assumptions)
  </success_criteria>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.