ca-feature
From the author
Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval.
Install
npx skills add arbiterForge/codeArbiter --skill ca-feature -a claude-code
Installs to .claude/skills/ca-feature/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (AGPL-3.0) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-a-featuretestdouble/hanBuilds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not plan a restructure of code that already exists — use plan-a-change. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research. Does not map the bounded contexts of existing code — use ddd-analysis.Planning★ 327
- ca-sprintarbiterForge/codeArbiterRun an autonomous sprint from maintained specs and plans, with truthful verification and no duplicate artifact approval ceremonies.Planning★ 149
- brainstormingarbiterForge/codeArbiterRefine feature and sprint intent into a useful specification. Capture scope, observable criteria and material choices without repeated artifact approval ceremonies.Planning★ 149
- spec-creationa5c-ai/babysitterFeature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.Planning★ 1.9K
- writing-planssandbaseai/sandbase-skillsPlan, implement, or review writing plans work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests writing plans work.Writing★ 202
- plan-implementationtestdouble/hanBuilds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.Planning★ 327
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in