plastic-intent-speccing

Solid

Consolidate 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).

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Intent Speccing Consolidate the enriched Why into `spec.md` through eight fixed steps, one action per step. The next action is never a judgment call: when a section cannot be filled from what is on record, step 5 is to stop and ask, never invent. ## Precondition Run only when the active intent is at Why (its `## Intent` and enriched `## Context` plus `### Decisions` exist, `spec.md` does not yet exist or is being redone) and the user has asked to consolidate that Why into the spec. If no intent is active, or the active intent is not at Why, report that and stop; do not guess which intent is meant. ## The 8-step sequence | Step | Action | |---|---| | 1 | Confirm the precondition above. | | 2 | Read inputs in fixed order and build a ruling ledger: (a) `## Context` and `### Decisions`; (b) `## Insights` newest-last, so a later ruling supersedes an earlier conflicting one; (c) `resources/discovery--<slug>.md`; (d) any other `resources/*.md`. | | 3 | Decide the tier: adopt the brainstorming `Tier:` recommendation from Decisions or Insights; otherwise apply the PLASTIC.md tiers rubric (S = single mechanism or file cluster, M = one subsystem, L = cross-cutting or novel design). | | 4 | Fill the template section by section, all 8 sections in template order. Read `references/per-section-fill-rules.md` now, filling the template is the trigger. Write the tier as the literal top line above `# Spec:`. Encode every ruling into its matching section, later supersedes earlier on confli...

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