fidraft-capture

Capture deferred ideas with timestamps and context into a structured draft file.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/lukeivers/loam --skill fidraft-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fidraft-capture
Source: https://github.com/lukeivers/loam/tree/main/plugins/dev-sdlc/skills/fidraft-capture
Command: npx skills add https://github.com/lukeivers/loam --skill fidraft-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users quickly capture deferred ideas, improvements, or feature opportunities during development sessions, preventing loss of valuable insights.

Core Features & Use Cases

  • Idea Capture: Efficiently record future-oriented ideas and insights directly into a structured draft file.
  • Traceability: Include timestamps, provenance, and sources to ensure clear context.
  • Use Case: During a coding session, when an improvement opportunity arises, use this Skill to immediately document it with relevant details for future review.

Quick Start

Use the fidraft-capture skill to record a new future idea related to upcoming feature enhancements in your workflow.

Frequently Asked Questions about fidraft-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture future ideas and improvements mid-workflow without losing context?

This approach records future-oriented ideas into a structured draft file during active sessions, preserving the immediate context and timestamp to prevent loss of valuable insights.

What is the best way to document deferred feature ideas during a coding session?

Recording deferred feature ideas during a coding session involves immediately logging the suggestion, its provenance, and source details into a structured draft file for later review.

How do I ensure traceability when logging future development suggestions?

To ensure traceability when logging future development suggestions, include timestamps, provenance, and source information alongside the captured idea in the documentation file.

Do I need any specific dependencies to set up idea capture for my development workflow?

No specific dependencies are required to set up idea capture for your development workflow, as the Skill operates independently using only its internal scripts and references.

When should I use a structured draft file for idea documentation instead of a general note?

You should use a structured draft file for idea documentation when you need to capture future-oriented insights mid-flow with specific context, timestamps, and provenance for future processing.