Agent skill
implement-feature-common-member-nightrip
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/implement-feature-common-member-nightrip
SKILL.md
Implement Feature with SDD
Feature: $ARGUMENTS
Follow the Spec Driven Development workflow strictly. Do NOT skip any step.
Step 1: Explore (Read Before Writing)
Understand the codebase before writing anything:
- Read the relevant issue if a number was provided:
gh issue view $ARGUMENTS - Read related models in
app/models/ - Read existing specs for similar features in
spec/ - Check
config/routes.rbfor existing routes - Check
spec/factories/for available factories
Summarize what you found: what exists, what needs to be added.
Step 2: Write Failing Specs First
Before writing any implementation code, write RSpec specs:
Model specs (if adding model logic)
- File:
spec/models/<model>_spec.rb - Test validations, associations, scopes, and methods
Request specs (if adding controller actions)
- File:
spec/requests/<resource>_spec.rb - Test HTTP status, authentication, authorization
System specs (if adding user-facing features)
- File:
spec/system/<feature>_spec.rb - Test user flow with Capybara
Run specs to confirm they fail:
bundle exec rspec <spec-file> --format documentation
Show the failing output. If specs pass without implementation, they're testing the wrong thing.
Step 3: Implement
Write minimal code to pass the specs:
- Generate model/migration if needed:
bin/rails generate model ... - Run migrations:
bin/rails db:migrate - Add model logic (validations, associations, methods)
- Add controller actions with proper authentication/authorization
- Add views using ERB + Turbo Frames/Streams
- Add Stimulus controller if JavaScript behavior is needed
Follow existing patterns — read similar code first.
Step 4: Verify
Run specs after implementation:
# Run the new specs
bundle exec rspec <spec-file> --format documentation
# Run full test suite
bundle exec rspec
# Auto-fix linting
bin/rubocop -a
# Security scan
bin/brakeman --no-pager
All steps must pass before creating a PR.
Step 5: Report
Summarize:
- What specs were written (file paths)
- What was implemented (files changed)
- Test results (pass/fail counts)
- Any rubocop or brakeman findings
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?