BumpyClock/agent-templates / skills/programming
programming
UnverifiedImplement, debug, refactor, or review code with scoped changes and evidence.
references/workflows/feature.md
View on GitHub# Feature
Use for a new or changed behavior that needs coordinated implementation.
For a small, clear change, use the same contract and evidence without this workflow.
## Workflow
1. Define the requested behavior, authorized scope, affected consumers, and compatibility requirements. Identify what observation will establish completion.
2. Inspect the current owners and integration points. Resolve material design uncertainty before dependent edits.
3. Implement a coherent unit through its consumers. Preserve existing behavior outside the contract.
4. Assess the implemented behavior against the completion observation and affected consumer contracts. Correct material gaps before completion.
5. Report the behavior delivered, consequential decisions, and unresolved limits. Separate completed work from proposed work.
## Design decisions
Use [Model the Domain](../../../pstack/principle-model-the-domain/SKILL.md) when state or repeated shape assumptions need a representation.
Use [Foundational Thinking](../../../pstack/principle-foundational-thinking/SKILL.md) when several consumers depend on one prerequisite.
Use [Experience First](../../../pstack/principle-experience-first/SKILL.md) for consumer tradeoffs.
Use [architecture guidance](../architecture/architecture-planning.md) when boundaries or contracts need a decision.
Choose the representation before dependent logic when scattered flags or repeated branches obscure the domain.
For upstream-derived code, compare the source revision before edits and carry shared-primitive changes through every affected consumer.
When relevant, check the integration paths that commonly drift:
- Creating and resuming, loading, or restoring the same feature preserve the intended state.
- Enabling and disabling a gate or option apply compatible behavior.
- A reused helper preserves the information and side effects required by the new caller.
- Removing a producer does not silently remove the only source of a required effect.
Use [Delegate After the Contract](../../../pstack/principle-delegate-after-the-contract/SKILL.md) when parts could run in separate contexts or on a less capable model.
## Limits
Ordinary function calls do not require parallel design exploration.
A feature request does not itself authorize commits, pull requests, deployment, or unrelated cleanup.
For a prototype-only request, use the [prototype skill](../../../engineering/prototype/SKILL.md) and stop at the requested decision.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |