shaping

Translate brainstorming outcomes into a PR-ready implementation plan using vanilla-rails patterns.

3|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/ZempTime/zemptime-marketplace --skill shaping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/ZempTime/zemptime-marketplace/tree/main/vanilla-rails/skills/shaping
Command: npx skills add https://github.com/ZempTime/zemptime-marketplace --skill shaping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use after brainstorming to apply vanilla-rails patterns to a feature, producing a structured handoff for implementation planning.

Core Features & Use Cases

  • Apply vanilla-rails patterns to determine scope, artifacts, and a clear work breakdown for a feature.
  • Produce PR-ready decisions and a plan for the engineering team.
  • Use Case: after a brainstorming session for a feature, run shaping to generate scoped tasks, naming, and model/controller decisions.

Quick Start

Run /shape after brainstorming to generate a structured plan and PR-ready handoff.

Frequently Asked Questions about shaping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate brainstorming outcomes into a vanilla-rails implementation plan?

To translate brainstorming outcomes into a vanilla-rails implementation plan, you apply structured pattern decisions for data-modeling, controllers, and naming conventions to generate a PR-ready work breakdown document.

What is the best way to scope a feature into PR-ready tasks using vanilla-rails patterns?

Scoping a feature into PR-ready tasks using vanilla-rails patterns involves defining the scope, required artifacts, and a phased work breakdown to enforce concrete decisions for models and controllers.

Can I use this to generate model and controller naming patterns for a new Rails feature?

Yes, you can generate model and controller naming patterns for a new Rails feature by enforcing concrete pattern decisions during the shaping process to produce a structured handoff plan.

When do I need to run feature shaping for a structured work breakdown?

You need to run feature shaping for a structured work breakdown after completing a brainstorming session, using the outcomes to determine scope, artifacts, and phased implementation tasks for your engineering team.

Does this approach require a completed brainstorming session before generating a plan?

Yes, this approach requires a completed brainstorming session because it uses those outcomes as input to apply vanilla-rails patterns and produce a ready-to-action implementation plan document.