Feature Ticket Proposal

0•

Researches and pressure-tests rough feature ideas through codebase feasibility analysis, assumption tracking, and collaborative scoping before ticket creation.

Propose Ticket acts as an investigative thinking partner that validates feature requests before they are converted into formal work items. By scanning repository architecture, tracing caller dependencies, inspecting existing test suites, and cross-referencing external documentation, it uncovers hidden assumptions, architectural contradictions, and silent breaking changes. Rather than jumping directly to implementation, this skill collaborates with developers through targeted questioning to weigh implementation trade-offs and reach a shared consensus, ensuring clean handoffs to ticket creation tools without writing unverified code.

Key Features

01Deep codebase feasibility research tracing symbols, consumers, and invariant test specs
020 GitHub stars
03Strict guardrails preventing premature ticket generation or code modification
04Surfaces hidden assumptions, framing mismatches, and architectural contradictions
05Categorizes open questions into user decisions, research tasks, and follow-up tickets
06Formulates concrete implementation options with trade-off analysis and recommendations

Use Cases

01Scoping complex feature requests to identify edge cases and dependency risks before sprint planning
02Evaluating architectural trade-offs across multiple technical implementation paths
03Aligning developer mental models with actual codebase patterns prior to drafting tickets