skills.rest
BrennonTWilliams
BrennonTWilliamsCOMMUNITY
Explore all skills by this author →
GitHub

ll-go-no-go

Assess software issues and sprint tasks for implementation readiness.

7|2|Updated Jan 3, 2026
Search Tags:#software engineering#code review#issue management#decision support#adversarial#go-no-go
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-go-no-go
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ll-go-no-go
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-go-no-go
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-go-no-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the uncertainty and lack of rigor in deciding whether a software issue is ready for implementation or worth the engineering effort.

Core Features & Use Cases

  • Adversarial Review: Provides a critical, objective assessment of proposed tasks to identify potential pitfalls or scope creep.
  • Decision Support: Evaluates whether an issue is technically sound and aligned with project goals before development begins.
  • Use Case: Use this before starting a complex refactor to ensure the proposed approach is robust and the issue is clearly defined.

Quick Start

Ask the agent to perform a go no go review on the issue with ID 102 to determine if it is ready for implementation.

Frequently Asked Questions about ll-go-no-go

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

FAQPage Schema
How do I perform a go/no-go assessment for a software issue before implementation?▼

A go/no-go assessment validates software issue readiness by analyzing project history, issue context, and codebase state to determine technical viability and alignment with project goals before development begins.

What is adversarial code review for issue management and when do I need it?▼

Adversarial code review provides a critical, objective assessment of proposed sprint tasks to identify potential pitfalls or scope creep. You need it before starting complex refactors to ensure the proposed approach is robust.

Can I use decision support tools to check if a complex refactor is ready for development?▼

Yes, decision support tools evaluate whether a software issue is technically sound and clearly defined. They analyze project history and codebase state to provide a feasibility review for complex refactors.

What's the best way to identify scope creep and pitfalls in proposed sprint tasks?▼

Adversarial review is the best way to identify scope creep and pitfalls in sprint tasks. It provides a critical, objective assessment of proposed issues to validate implementation readiness and ensure technical soundness.

Do I need issue tracking and git history tools to perform a feasibility review?▼

Yes, performing a comprehensive feasibility review requires access to issue tracking and git history tools. These tools provide the project history and issue context needed to determine project viability.

Why does my software issue lack rigor in deciding if it is worth the engineering effort?▼

Your software issue lacks rigor due to uncertainty in deciding implementation readiness. An adversarial go/no-go assessment provides objective validation by analyzing codebase state and project history to determine viability.

Related Skills

Explore More Software Engineering Skills→
g-bastianellig-bastianelli

greet

Detect Linear issue identifiers and prepare context for planning.

Community
Intermediate
EricOo0EricOo0
6

receiving-code-review

Verify code-review feedback against the codebase before implementing incremental tested changes.

Community
Advanced
carson-sweetcarson-sweet
6

Session Export

Generate a portable markdown record of an AI session with transcripts and decision logs.

Community
Intermediate
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced