スキル 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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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)
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: 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.