gjalla-breakdown
Break Features Into Implementation Waves
Large feature specifications can be difficult to sequence and track. This skill creates dependency-ordered waves of small tasks with files and acceptance checks.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "gjalla-breakdown" from https://skillstore.io/skills/gjalla-gjalla-breakdown.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-breakdown/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„gjalla-breakdown“ wird verwendet. Add email verification to account registration.
Erwartetes Ergebnis:
- Wave 1: Add verification fields and migration, with schema checks as acceptance criteria.
- Wave 2: Create token generation and delivery tasks that depend on the schema update.
- Wave 3: Add verification endpoints, user interface changes, tests, and documentation.
„gjalla-breakdown“ wird verwendet. Add saved dashboard filters for signed-in users.
Erwartetes Ergebnis:
- W1-T1: Define stored filter data and persistence behavior.
- W2-T1: Add service operations after the data model is available.
- W2-T2: Build interface controls in parallel with service integration tests.
- W3-T1: Complete end-to-end verification and documentation.
Sicherheitsaudit
SicherThe single static finding is a false positive. SKILL.md contains planning guidance only, with no system reconnaissance, executable code, external commands, or prompt injection.
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/gjalla-gjalla-breakdown/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/gjalla-gjalla-breakdown?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/gjalla-gjalla-breakdown?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-breakdown/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-breakdown.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
gjalla. (2026). gjalla-breakdown security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-breakdown/audits/1BibTeX-Zitat
@techreport{gjalla-gjalla-gjalla-breakdown-2026,
author = {gjalla},
title = {gjalla-breakdown security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-breakdown/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-breakdown 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-breakdown/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-breakdown:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Plan a Feature Implementation
Convert an approved specification into sequenced tasks that are easy to assign, implement, and verify.
Coordinate Parallel Work
Identify independent tasks that multiple contributors can complete during the same implementation wave.
Prepare Agent Execution
Create a structured implementation plan with clear files, dependencies, and acceptance checks for coding agents.
Diese Prompts ausprobieren
Break this feature specification into dependency-ordered waves. Give each task an ID, description, files, dependencies, and acceptance check: [specification]
Review this specification and repository context. Produce implementation waves with tasks touching one or two files each: [specification and repository context]
Break down this specification for parallel delivery. Minimize dependencies within each wave and include tests, documentation, and verification: [specification]
Create a wave plan for this complex feature. Explain dependencies, flag uncertain file ownership, and split the work if it exceeds 20 tasks: [specification]
Bewährte Praktiken
- Provide the approved specification and relevant repository context before requesting a breakdown.
- Keep each task small enough to produce a focused, reviewable change.
- Review file paths, dependencies, and acceptance checks before implementation begins.
Vermeiden
- Do not use vague requirements that omit expected behavior or technical constraints.
- Do not combine unrelated modules into one large task without a clear dependency reason.
- Do not treat tasks within one wave as parallel when they depend on each other.