feature
Full SDLC orchestrator from specification to deployment. Guides through all stages with quality gates.
12 stars
Best use case
feature is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full SDLC orchestrator from specification to deployment. Guides through all stages with quality gates.
Teams using feature should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/feature/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/feature/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/feature/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How feature Compares
| Feature / Agent | feature | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Full SDLC orchestrator from specification to deployment. Guides through all stages with quality gates.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Feature Skill Complete SDLC orchestration with quality gates. ## When to Activate This skill is relevant when: - Implementing complete features end-to-end - Need full SDLC process guidance - Want structured feature delivery - Require quality gates at each stage ## Core Principles ### Process Discipline - Follow SDLC stages in order - Don't skip steps - Each stage builds on previous - Systematic progression ### Quality Gates - Get approval before proceeding - Validate completeness at each stage - User confirms readiness - Prevent rework from rushing ### Clear Communication - Summarize progress at transitions - Document what was completed - Explain what comes next - Keep stakeholders informed ### Stage Completeness - Finish current stage fully - Don't mix stage concerns - Clear artifacts per stage - Traceable progress ## Quick Checks For complete feature delivery, verify: - [ ] Feature request is clear - [ ] Codebase access available - [ ] Stage 1: Specification created and approved - [ ] Stage 2: Clarifications addressed and confirmed - [ ] Stage 3: Implementation plan created and reviewed - [ ] Stage 4: Tasks broken down and confirmed - [ ] Stage 5: Implementation complete, reviewed, and quality-checked - [ ] Stage 6: Changes committed and deployed - [ ] Stage 7: Retrospective documented - [ ] All quality gates passed - [ ] All tests passing - [ ] User approval at each gate ## SDLC Stages ### Stage 1: Specification - Create product specification - Define requirements clearly - Get user approval ### Stage 2: Clarification - Review spec for gaps - Address questions - Confirm completeness ### Stage 3: Planning - Create implementation plan - Get architectural review - Obtain plan approval ### Stage 4: Task Breakdown - Break down into actionable items - Confirm task list complete ### Stage 5: Implementation - Execute the plan - Code review validation - Quality verification - All tests pass ### Stage 6: Delivery - Commit changes - Deploy (if applicable) ### Stage 7: Retrospective - Document lessons learned - Capture improvements
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.