devflow-file-standards
Standardize DevFlow Files
DevFlow projects need consistent file names, directories, and metadata. This skill gives Claude, Codex, and Claude Code shared standards for requirements and bug workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "devflow-file-standards" from https://skillstore.io/skills/dimon94-devflow-file-standards.md and its manifest at https://skillstore.io/api/skills/dimon94-devflow-file-standards/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "devflow-file-standards". Where should the PRD for REQ-042 be stored?
Expected outcome:
The response identifies the requirement folder and states that the PRD belongs with the other REQ-042 workflow documents.
Using "devflow-file-standards". Review my task IDs and labels for a DevFlow task list.
Expected outcome:
The response confirms valid task ID formatting, explains parallel labels, and flags labels that do not match the standard.
Using "devflow-file-standards". Check whether my workflow status fields are complete.
Expected outcome:
The response lists missing tracking fields, verifies the workflow phase, and notes any status value that is not allowed.
Security Audit
SafeThe skill is documentation-only, and the static hits are caused by Markdown fences, inline paths, and examples. I found no executable code, network behavior, hidden-file reads, environment file reads, prompt injection text, or malicious intent in SKILL.md.
Risk Factors
⚙️ External commands (57)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dimon94-devflow-file-standards/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dimon94-devflow-file-standards?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dimon94-devflow-file-standards?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-devflow-file-standards/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dimon94-devflow-file-standards.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dimon94. (2026). devflow-file-standards security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimon94-devflow-file-standards/audits/8BibTeX citation
@techreport{dimon94-dimon94-devflow-file-standards-2026,
author = {Dimon94},
title = {devflow-file-standards security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimon94-devflow-file-standards/audits/8},
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: "devflow-file-standards security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimon94"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dimon94-devflow-file-standards/audits/8"
identifiers:
- type: other
value: "skillstore:dimon94-devflow-file-standards:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Align Flow Commands
Use shared paths, identifiers, and status names when creating or updating DevFlow commands.
Guide Agent Outputs
Keep generated PRD, design, epic, and task files consistent across multiple agents.
Review Project Structure
Check whether a requirement or bug workspace follows the expected DevFlow layout.
Try These Prompts
Use this skill to tell me where a DevFlow PRD file should be placed for requirement REQ-123.
Review these DevFlow file and directory names against the skill standards, then list any corrections.
Compare my PRD, TECH_DESIGN, EPIC, and TASKS frontmatter fields with the required DevFlow standards.
Audit this DevFlow requirement workspace for naming, directory structure, frontmatter, status fields, and special file handling.
Best Practices
- Use one requirement ID consistently across paths, branch names, status files, and documents.
- Keep generated workflow files in the documented requirement or bug folder structure.
- Check frontmatter before handoff so downstream agents can parse status and metadata.
Avoid
- Mixing requirement IDs from different workspaces in one file tree.
- Adding agent-specific writing rules to this shared file standards reference.
- Committing environment files, secrets folders, or dependency folders inside DevFlow workspaces.