quick-dev

name	quick-dev
description	Implement task directly with AI SDLC standards awareness (no planning mode)

Quick Development with Standards Awareness

Implement a task directly without entering planning mode, while still applying project standards from .agyflow/docs/.

Usage

/agyflow:quick-dev [task description]

Examples

/agyflow:quick-dev "Add a logout button to the navbar"
/agyflow:quick-dev "Fix the typo in the error message"
/agyflow:quick-dev "Update the API endpoint to accept JSON"

---

When to Use

Use /agyflow:quick-dev when:

• Task is clear and well-defined
• You know what needs to be done
• No architectural decisions needed
• Quick fixes, small features, or straightforward changes

Use /agyflow:quick-plan instead when:

• Task scope is uncertain
• Multiple implementation approaches possible
• Architectural decisions required
• You want user approval before coding

---

Workflow

Step 1: Parse Input

Get the task description:

• If provided as argument, use it directly
• If not provided, use question to prompt:

  "What would you like to implement? Please describe the task."
  

Step 1b: Create Task Directory

Create a lightweight task directory for artifact anchoring.

1. Generate a task name from the task description:
   • Extract 3–5 key words, convert to lowercase kebab-case
   • Prepend today's date: YYYY-MM-DD-kebab-name
   • Examples: "Add a logout button to the navbar" → 2026-05-28-add-navbar-logout-button, "Update the API endpoint to accept JSON" → 2026-05-28-update-api-accept-json
2. Create directory: .agyflow/tasks/quick-dev/YYYY-MM-DD-task-name/
3. Write task.yml with initial state using the template src/templates/quick-dev-task.yml.

Step 2: Discover Standards

Check if .agyflow/docs/INDEX.md exists:

If exists:

1. Read INDEX.md to discover available documentation and standards
2. Identify which standards are relevant based on:
   • The categories and files listed in INDEX.md
   • The nature of the task
   • Keywords in the task description
3. READ the applicable standard files (see Standards Reading Enforcement below)
4. Update task.yml: Add paths of standards read to standards_applied list

If not exists:

• Note that no standards are available
• Suggest running /agyflow:flow-init in completion message

Standards Reading Enforcement (MANDATORY)

BLOCKING: Reading INDEX.md alone is NOT sufficient. You MUST read actual standard files.

Enforcement Process:

1. Read INDEX.md to discover available standards
2. Identify which standards apply based on task description
3. READ each applicable standard file using Read tool (not just note it exists)
4. Apply standards during implementation
5. List applied standards in completion summary

Examples of standard discovery:

• Task mentions "upload" → Read file-handling standards
• Task mentions "form" → Read validation and accessibility standards
• Task mentions "API" → Read api and error-handling standards

Step 3: Implement with Standards

MANDATORY: During implementation:

1. Explore the codebase to understand context (using Glob, Grep, Read)
2. Apply discovered standards - Reference the standard files you read
3. For each code change, verify it follows applicable standards
4. If you encounter new areas while coding (e.g., auth, database), read applicable standards before proceeding
5. Make the necessary code changes
6. Run relevant tests if applicable

Step 4: Verify Standards Compliance

After implementation, verify:

1. Review changes against applicable standards
2. Confirm key guidelines were followed
3. Note any standards that were applied

Step 5: Summary

Write summary.md in the task directory:

# Task Summary

**Skill**: quick-dev
**Date**: YYYY-MM-DD
**Status**: completed

## What Was Done

[What was implemented]

## Files Modified

- `path/to/file`

## Standards Applied

- [standard]: [guideline]

## Tests

- [test file] — [result]

## Commit Suggestion

[conventional commit message]

Update task.yml: set status: completed, updated: [now].

Provide completion summary to user:

• What was implemented
• Which standards from INDEX.md were applied
• Any tests run and their results
• Suggestions for follow-up (if any)

---

What This Does

1. Parses task description from user input
2. Creates lightweight task directory with task.yml for artifact anchoring
3. Discovers applicable standards from .agyflow/docs/INDEX.md
4. READS actual standard files (MANDATORY - not just INDEX.md)
5. Implements directly without planning mode approval
6. Verifies standards were followed
7. Writes summary.md in task directory and updates task.yml to completed
8. Summarizes what was done and which standards were read and applied

Graceful Fallback

If .agyflow/docs/ does not exist:

Proceed with implementation normally, then note:

"No AI SDLC standards found. Consider running `/agyflow:flow-init` to initialize
project documentation and coding standards for better consistency."