docs: Update README and plans documentation for clarity and organization

docs/README.md

@@ -3,7 +3,8 @@
 - `guides/` contains user guides and practical project workflows.
 - `architecture/` describes implemented systems and maintained technical references.
 - `specs/` contains feature specifications, including completed phase specs.
-- `plans/` is for active and future implementation plans.
+- `ideas/` contains the live backlog of future feature ideas.
+- `plans/` contains accepted phase design briefs and active or future implementation plans.
 - `archive/` preserves older project references and completed plan drafts.
 - `known_issues.md` tracks current bugs and deferred fixes.
 

docs/ideas/feature_backlog.md

@@ -0,0 +1,23 @@
+# Feature Backlog
+
+This is the live list of future Stickman Studio feature ideas. Designer maintains it as ideas become clear in discussion with the user.
+
+## Suggested order
+
+Priorities are recommendations for discussion, not a committed release schedule. Keep higher-priority items first and explain the reason for each ranking.
+
+No feature ideas have been captured yet.
+
+## Entry format
+
+For each feature, record:
+
+- **Status:** Idea, Exploring, Planned, or Parked
+- **Suggested priority:** High, Medium, or Low
+- **Intent:** The user goal or experience the feature should support
+- **Rationale:** Why it may be valuable and how it fits the project
+- **Connections:** Relevant project docs, code, and dependencies, when known
+
+## Historical context
+
+The [archived roadmap](../archive/ROADMAP.md) is historical material, not an active priority list. Revisit individual ideas from it only when they are relevant to a current discussion.

docs/plans/README.md

@@ -1,3 +1,7 @@
-# Active plans
+# Active plans and design briefs
 
-Place future implementation plans in this directory. Move completed or superseded plan drafts to `../archive/plans/`.
+Keep accepted Designer handoff briefs and future implementation plans in this directory. Name phase briefs `phase_<number>_<feature_slug>.md` and title them `Phase <number> — <Feature>`.
+
+Designer briefs capture the product goal, user experience, scope, success criteria, and questions for the spec-pipeline. They are planning inputs, not final architecture specifications; the architect writes those in `../specs/`.
+
+Move completed or superseded plan drafts to `../archive/plans/`.