Plan and scope new software features with requirements and acceptance criteria.
npx skills add https://github.com/CuongTran69/tramthientra --skill feat-cuongtran69
Please help me install this Agent Skill. Skill: feat Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/feat Command: npx skills add https://github.com/CuongTran69/tramthientra --skill feat-cuongtran69
This Skill helps teams and individual contributors turn vague or incomplete feature requests into a clear, scoped, and implementable plan so work can be estimated, assigned, and delivered with minimal rework. It reduces ambiguity by enforcing requirement simplification, discovery questions, and objective acceptance criteria so engineering and product align before coding begins.
Use the feat skill to explore and size a proposed feature by summarizing the requirement, listing three clarifying questions, and recommending an implementation approach.
High-intent search queries and answers about installing and using this skill.
Feature scoping from vague requests requires restating requirements in plain language, generating clarifying questions, and performing codebase investigation to map integration points and surface hidden implementation complexity before development begins.
Estimating feature implementation effort involves analyzing the codebase for existing patterns, comparing multiple architecture approaches, identifying tradeoffs, and producing verifiable acceptance criteria to assess risk and complexity objectively.
Turning product requirements into developer-ready specifications involves simplifying requests through discovery questions, mapping architecture integration points, and generating a zero-fog checklist with objective acceptance criteria for engineering alignment.
Yes, you can compare implementation approaches by evaluating tradeoffs, generating architecture diagrams, and recommending a specific path with verifiable acceptance criteria to ensure product and engineering teams align before coding begins.
Feature planning fails without alignment because ambiguous requirements cause rework; enforcing requirement simplification, targeted clarifying questions, and objective acceptance criteria ensures engineering and product share a clear, scoped, and implementable plan.
Codebase investigation is needed during feature discovery to identify relevant modules, map existing integration patterns, estimate development effort, and surface hidden complexity that impacts the final implementation plan and risk assessment.
JmarquesGuide users in shaping raw text into structured articles paragraph by paragraph.
phoenixvcGenerate step-by-step implementation plans with acceptance criteria and rollback procedures.
nullmastermindPlan maintenance work by exploring scope and assessing impact.
HerxinsasaBreak down project plans into vertical slice issue tracker tickets.
