plastic-intent-speccing
SolidConsolidate the enriched Why (`## Context`, `### Decisions`, `## Insights`) into `spec.md` through a deterministic, judgment-free numbered sequence. Use when the user types the command to turn the brainstorm into a spec, asks to "write the spec", "spec this intent", "consolidate into spec.md", or the active intent is at Why with enough Decisions on record to close it out. Also fires on an indirect request that never names spec.md, such as "turn what we just discussed into the contract the planner builds from." Distinct from `plastic-intent-brainstorming` (the exploration that produces the enriched Why, upstream of this skill) and `plastic-intent-planning` (turns an existing spec.md into plan.md for How, downstream of this skill).
Install
Quality Score: 80/100
Skill Content
Details
- Author
- zalom
- Repository
- zalom/plastic
- Created
- 2 months ago
- Last Updated
- 1 weeks ago
- Language
- Ruby
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
plastic-intent-brainstorming
Explore intent requirements and design before implementation, through conversational prose questions asked one at a time (no multiple-choice chips), persisting each owner ruling immediately as an insight. Produces the enriched Why (Context and Decisions) in the active intent directory; hands off to /plastic-intent-speccing for spec.md.
plastic-intent-planning
Write implementation plans from a spec. Produces plan.md, checklist.md, and at least one real actions/ACTION_N.md (every tier) in the active intent directory.
specdd
Spec-driven development orchestrator that turns vague, top-of-mind feature requests into production-grade specifications before any code is written. ALWAYS use this skill whenever the user describes a feature, change, capability, screen, flow, or new component in plain language — even if they don't explicitly ask for a spec. Triggers on phrases like "build me", "make me", "add a feature", "I want to", "help me create", "implement", "let's build", "I need a", "can you make", "create a screen/page/component", or any new-feature request that lacks complete requirements (missing user stories, acceptance criteria, edge cases, error/empty/loading states, accessibility, or non-functional requirements). Interviews the user to fill gaps, applies UX/UI common sense, produces a structured spec + plan + tasks, then implements against the spec. Use this BEFORE writing any code for non-trivial features. Skip only for true one-liners (rename a variable, fix a typo, answer a research question) or work that is purely investig