技能 gjalla-spec
📦
gjalla-spec
内容修订 r1 安全 ⚙️ 外部命令
Create Production-Ready Software Specifications
Complex features fail when requirements, architecture effects, and verification criteria remain unclear. This skill guides agents through research and produces an implementation-ready Gjalla specification.
支持: Claude Codex Code(CC)
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
智能体请求
Review the Skillstore skill "gjalla-spec" from https://skillstore.io/skills/gjalla-gjalla-spec.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“gjalla-spec”。 Plan account deletion across authentication, billing, and analytics services.
预期结果:
- Problem: Account deletion behavior is inconsistent across services.
- Goal: Remove personal data while preserving legally required billing records.
- Approach: Coordinate deletion events, retention rules, retries, audit records, and service ownership.
- Verification: Test complete deletion, partial failures, retries, retention exceptions, and rollback.
正在使用“gjalla-spec”。 Specify a gradual migration from synchronous notifications to a queue.
预期结果:
- Non-goal: Replacing notification providers is outside this migration.
- Architecture delta: Producers publish durable jobs while workers handle delivery and retries.
- Dependencies: Queue infrastructure, observability, idempotency keys, and deployment sequencing.
- Rollback: Route producers back to synchronous delivery while safely draining queued jobs.
安全审计
安全v1 • 2026/8/11 打开版本化报告
The only static finding is a false positive caused by Markdown backticks around a Gjalla CLI command. The prompt contains no executable code, prompt injection, or malicious intent.
1
已扫描文件
30
分析行数
0
复核项
0
已忽略误报
风险因素
⚙️ 外部命令 (1)
最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。
审计者: codex
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/gjalla-gjalla-spec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/gjalla-gjalla-spec?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/gjalla-gjalla-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-spec.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
gjalla. (2026). gjalla-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-spec/audits/1BibTeX 引用
@techreport{gjalla-gjalla-gjalla-spec-2026,
author = {gjalla},
title = {gjalla-spec security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-spec/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gjalla-spec security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "gjalla"
date-released: "2026-08-11"
url: "https://skillstore.io/skills/gjalla-gjalla-spec/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-spec:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中 55
架构
85
可维护性
87
内容
65
社区
91
规范符合性
你能构建什么
Plan a Cross-Service Feature
Map architecture effects, data flows, dependencies, rollback steps, and tests before changing multiple services.
Define Acceptance Criteria
Turn a product problem into explicit goals, non-goals, observable behaviors, and acceptance tests.
Prepare an Implementation Handoff
Create a concise reference specification that gives delivery teams shared technical and verification guidance.
试试这些提示
Draft a Feature Specification
Create a Gjalla specification for [feature]. Research the current architecture, ask necessary questions, and define goals, requirements, approach, tests, dependencies, and rollback.
Clarify an Ambiguous Request
Investigate the current system around [problem]. Identify missing decisions, ask focused questions, then draft a specification with explicit non-goals and verification criteria.
Plan a System Migration
Plan the migration from [current state] to [target state]. Cover architecture deltas, data flows, sequencing, dependencies, compatibility, verification, and rollback.
Assess Second-Order Effects
Create an advanced change specification for [proposal]. Trace downstream effects, failure modes, operational risks, boundary constraints, phased delivery, acceptance tests, and rollback triggers.
最佳实践
- Provide the problem, affected systems, constraints, and relevant Gjalla project context.
- Resolve decisions that change the technical approach before approving the specification.
- Make every behavioral requirement observable and pair it with a verification method.
避免
- Do not approve a specification that assumes undocumented architecture or missing dependencies.
- Do not combine goals, implementation details, and verification into vague narrative paragraphs.
- Do not omit rollback planning for changes that affect production data or shared services.
常见问题
What does this skill produce?
It produces a structured change specification covering the problem, scope, requirements, technical approach, verification, dependencies, and rollback.
Does it require Gjalla?
Yes. Its intended workflow uses Gjalla CLI or MCP to retrieve project context and create the canonical specification.
Will it implement the feature?
No. It prepares the approved plan before implementation begins.
Can it use Claude Plan or another plan format?
Yes. It can present an alternative planning format, then record approved information in a Gjalla specification.
When should I use it?
Use it before non-trivial features, migrations, architectural changes, or work with important dependencies and rollback requirements.
How does it handle missing information?
It researches available specifications and source code, then asks focused questions that affect the proposed solution.