implementing-stories
Implement using TDD Red-Green cycle. Focus on Red-Green only; refactoring is separate step.
Browse published AI skills maintained by kecbigmt. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
8Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Implement using TDD Red-Green cycle. Focus on Red-Green only; refactoring is separate step.
Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.
Execute codex CLI as sub-agent for thorough code reviews (codex's specialty), alternative approaches when stuck, or complex problems requiring extended investigation. Note that inference takes significant time.
Guide human PO through manual acceptance testing. Optional - use when PO wants manual verification before merge.
Epic design document template. Use when creating new epic documents or need epic structure reference.
Story log template for user stories. Use when creating new story documents or need story structure reference.
Pull request template for story-driven development. Use when creating PRs or need PR structure reference.
Commit, push, create PR. Use after verification passes and ready to share work for team review.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.