cy-create-spec
Create or update a requested CompozyOS spec and its applicable companion contracts, reusing current decisions and research. Not a prerequisite for ordinary coding tasks.
Install / Use
npx skills add kush-coder/autopilot-compozy --skill cy-create-specInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of cy-create-spec
cy-create-spec scores 62/100 on our quality scale, 403rd of 420 Education & Research skills we index.
Its SKILL.md is 4.5 KB long, lightly structured (1 heading) and no code examples: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
cy-create-spec compared with similar skills
All 4 of these similar skills score higher than cy-create-spec; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cy-create-spec (this skill)by kush-coder | 62 | 0 | — | SKILL.md |
| last30days-skillby mvanhorn | 100 | 68.2k | today | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install cy-create-spec?
- Run
npx skills add kush-coder/autopilot-compozy --skill cy-create-spec. The install tabs above show the steps for each supported agent. - Which AI agents does cy-create-spec work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is cy-create-spec safe to use?
- It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is cy-create-spec still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: cy-create-spec description: Create or update a requested CompozyOS spec and its applicable companion contracts, reusing current decisions and research. Not a prerequisite for ordinary coding tasks.
Create Spec
Use for a requested specification, not as a prerequisite to an ordinary fix. Author _spec.md with Product and Technical parts and the applicable companion contracts under .compozy/tasks/<slug>/.
-
Reuse the user's decisions, existing spec, and current research. Inspect relevant code/contracts for unresolved questions. Market research is needed only for a market/product uncertainty or an explicit request; delegation is optional and bounded.
-
State the motivating problem, observable outcome, scope, and non-goals. Ask focused questions only for decisions the evidence cannot settle, always in the format from
references/grill-protocol.md; apparent simplicity is not evidence. An approved direction satisfies the product checkpoint; do not repeat an interview or approval already completed. For an open-ended product interview, use the relevant branch ofreferences/grill-protocol.md. -
Write Part I and
_user_stories.mdfromreferences/spec-template.mdandreferences/user-stories-template.md. Product requirements may name a technology when it is an actual public contract or fixed user constraint; incidental implementation belongs in Part II. -
Define the changed public surface before its internal implementation:
_dx.mdusesreferences/dx-template.md; UI-bearing work uses_uiux.mdandreferences/uiux-template.md. For an internal-only spec, a brief no-public-surface entry is sufficient. Preserve named visual references and production owners. -
Write Part II with the concrete contracts the design changes. Read only relevant ADRs/analysis. Use
references/adr-template.mdfor consequential decisions with real alternatives; a routine choice needs no standalone ADR. Document the target project's compatibility policy for changed user state and public surfaces, including lossless migrations, deprecation/removal plans, delete targets, and one owning impact analysis with links from companions. If no policy exists, state the proposed guarantees and unresolved decisions explicitly. -
Write
_tests.mdusingreferences/tests-template.md: distinct invariants, owning suites, inputs/results, and necessary integration journeys. Reuse existing coverage; no quotas per component, error class, or layer. -
Write
_slices.md, the delivery order that spec delivery reads:| Slice | Layer | Depends on | Scope | Spec refs | | ----- | -------- | ---------- | --------------- | --------- | | S1 | backend | none | Export contract | US-001 | | S2 | frontend | S1 | Export dialog | US-002 |One row per independently verifiable slice.
Layernames the owning layer,Depends onlists slice IDs ornone, andSpec refscites the stories or sections it delivers. Choose slice count from dependencies and risk, and let unrelated slices run in parallel. The first slices should reach the earliest useful end-to-end outcome. -
Perform an inline self-check: verify that the motivating outcome is covered, public contracts agree across companions, changed interfaces use the project's language, each test invariant has an owning suite, every story belongs to a slice, slice dependencies are acyclic, and existing input/reference paths resolve in the target project or this skill's bundled resources. Mark new files and output destinations as planned; they need not exist before implementation. Record inapplicable sections and unresolved decisions explicitly. Check the earliest useful end-to-end outcome.
-
Save reviewable files and summarize unresolved decisions. After the user approves the saved spec, offer the optional peer review in
references/peer-review.md. Do not start implementation merely because spec writing is complete.
Templates are section guides: keep shared outcome/contract content, omit irrelevant sections or record a short reason where a downstream schema requires a slot. Read each reference when its branch is used, not the whole package. Maintain a concise File References index naming contract inputs and why each matters; slice briefs copy their relevant subset. Preserve requested scope; narrowing an accepted motivating problem requires the user's recorded decision.
For updates, edit affected sections/companions only. Missing or contradictory inputs are resolved from user decisions and current policy; report a genuinely blocking missing contract without inventing it.
Related Skills
last30days-skill
68.2kAI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
